[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

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.

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

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

SAP Logistics

Search This Blog