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

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button
Post a Comment
Read more

Stock Inconsistency Reports

Report: RM07KO01 - Stock consistency check between ML and IM Description : With the Stock Consistency Check report (RM07KO01), you can check the consistency of your stock data at company code level, valuation level, or material level. Possible errors in your stocks can thus be determined at an early stage before they cause major problems Transaction Code : CKMC - Consistency check between Material Master and Material Ledger
1 comment
Read more