Skip to main content

[SD] Understanding CRESTA Message type in distributed credit management

Message type 'CRESTA' (FM - IDOC_INPUT_CRESTA) is used to distribute the credit management information between SAP systems and Non-SAP to SAP systems in case of business uses central finance.

Standard SAP has provided transaction Code 'FCV1' is create A/R summary report which will subsequently generate CRESTA IDoc with customer credit information.

This program creates A/R summary data within a control area per credit account. This data can then be used either within distributed credit management, or in a non-distributed system.

CRESTA IDoc will not update the credit master data (FD32) in the the target system instead it will update A/R summary data in the credit master data.

In technical terms, System will not update table KNKK ( Credit Master data) instead it updates KNKKF* tables (Credit Management: FI Status Data).

While creating the sales order, system will perform credit check based on the data from AR summary data but not based on the credit master data.

Limitations :

Credit check based on the A/R summary data will not support Dynamic credit check functionality as time horizon will not be updated in the credit master data through CRESTA IDoc which is subsequently used in credit check while transaction processing.


Comments

  1. Unknown6 January 2021 at 01:33

    Shipsea logistics is the best logistic service provider over the worldwide. Shipsea provides logistics service provider along with high-end services like smart warehouse space around the globe. Get warehouse service, as a third-party logistics, we can design and implement the latest business policies of supply chain and solution from warehouse from a warehouse for an end-to-end distribution. Shispea is an end-to-end logistics service provider.

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more