[Change Documents] Change log for output condition records

Output condition records are crucial for business in the case of interfaces. Any changes to it will have an impact on the receiver system not receiving the data.

Standard SAP hasn't given any feature to capture records directly but however, SAP has given a provision to do so.

Below is the process to be recommended by SAP through SNOTE: 2967998 - No changelog available for OUTPUT condition records

Check the indicator for "Log Data Changes" for table NACH in SE11. (-> click button for Technical settings) This can be set.

You can develop your own query or Abap to read out the changes made in an output condition record. Use this information as a source:

If you create/change an output condition in MN04/MN05, an entry is written into the table B02* (e.g. B026) and into table NACH. The two tables are linked with B026-KNUMH=NACH-KNUMH.

Read table CDHDR where OBJECTCLAS = COND_OC and OBJECTID = NACH-KNUMH = B026-KNUMH

OBJECTID is stored in this format: 0000000001BEF026NEU where 0000000001=KNUMH, B=output, EF=Application (PO), 026=B026, NEU=output type

Then you can read table CDPOS with OBJECTCLAS = COND_OC and CHANGENR = CDHDR-CHANGENR

the simplest way is to execute OY18 and pass the NACH table. Transaction OY18 is used for analysis table entries as well,

Thank you.

Comments

[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.

[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

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...

SAP Logistics

Search This Blog