LO User Defined Z fields Delta - CMOD / SMOD

[Former Member]

Hello,

We have implemented various user defined Z fields in SD Orders/Deliveries/Billing extractor. All Z fields have been added only to extract structure and coded in CMOD include. Since this was a smaller BW customer, we were doing all daily full loads till now. Recently, we decided to switch to delta loads as size is growing. Upon switching to delta loads, we realized none of the Z fields delta is getting captured because of only extract structure changes.

Researching further, I see if the fields were delta relevant then we should have enhanced communication structures instead (MCVABK/MCVAP etc). I also read that we need to handle before / after images in SMOD include which gets executed while saving a document. This could be huge change considering we have lot of user defined fields.

Any simpler route to switch from extract structure to communication structure enhanced fields?

Thought there are lots of pieces on SDN, I couldn't find good sample code.

Thanks.

Abhijeet

[Colin4 · Accepted solution]

• When you make a change to a user-defined (enhanced) field using LBWE the new value is not extracted to BW with the delta load 
• An existing extract structure was enhanced using the append technique include user-defined fields. These are filled in user exit EXIT_SAPLRSAP_001. 
• Changes to these fields in the document are not extracted to BW if no additional field was changed that is contained as standard in the extract structure. 
• With deletion records (document or item was deleted), the user-defined field similarly remains empty.

A document change is effected in the delta extraction of applications
11, 12 and 13 by the transfer or two data records to BW.One of these
data records represents the status of the document before the change
(before image) and the other data record represents the status after the
change (after image).

During the extraction process, these two data records are compared by
the system and checked for changes. If there is no difference between the
before and after images, these data records do not continue to be
processed.
This means that the data records are not placed in the BW delta queue
(RSA7), since no field was changed in the relevant extract structure.

If the document change exclusively concerns a user-defined field that is
filled in EXIT_SAPLRSAP_001, this field is empty at the time of the
check, in both the before and after image.
Since there is no change for the system, the delta records are not
processed further.

A similar problem occurs if a document was deleted.
The document has already been deleted when EXIT_SAPLRSAP_001 is
executed.
The relevant data may not exist on the database at this time, depending
on the source from which the user-defined field is filled.

Example:

The field XBLNR is part of the append ZZMC13VD1ITM. That means that
the field is a user-defined field. You can find all the user-defined
fields in the table TMCEXCFZ but the standard fields are in the table
TMCEXCFS.

/SE16 TMCEXCFZ
CSTRUC                       FIELDNAME                      ESTRUC
MCVBRK                       XBLNR                          MC13VD0ITM

This field needs to be filled in the SAPI userexit EXIT_SAPLRSAP_001,
include ZXRSAU01.

Resolution

This reply cannot provide a generally applicable solution because the
solution varies greatly depending on which field was added to the
extract structure.

One way of filling user-defined fields is the following solution:

        Add the required fields to the the SD communication structures
        using the Append method and use the LIS customer exits to fill
        the field.

        For information on enhancing the communication structures, see
        the documentation for the enhancements MCS10001, MCS50001 and
        MCS60001 (provided in transaction SMOD).

        After you enhance the communication structures (for example
        MCVBAP), you can then enhance the extract structure (for example
        MC11VA0ITM) with the relevant field in the Customizing cockpit
        (transaction LBWE), provided that the comunication structure is
        available in the selection.

        To display a delta, you must make sure that you can determine the
        status in the user exit before and after the document change.

        This varies from case to case and depends on from which table the
        field is filled.

        For example, you may occasionally have to obtain the information
        from the internal document tables (such as xvbap and yvbap).

        Refer to note 216448 for information on correctly populating the
        before and after image.

   Another way of adding user-defined fields to extract structures
   is to enhance the document tables, for example, VBAK, VBAP, VBEP
   tc.

   The fields can be filled in the general sales user exits, the
   delivery or the invoice.
   The fields added using an append are also available in the
   LogisticCustomizing Cockpit for enhancing the extract structures.

   With the latter procedure, bear in mind that the fields added to
   the document tables must be saved to the database with the
   information they contain.
   An advantage of this method is that there is no need for data
   retrieval in the LIS UserExit.

See Also

note 1760322  This note shows you how to switch on a log for the application and you can see if the delta changes are been written to the delta queue.

The log is also useful if you can not find out who/what is making the changes to the field values.762951    Organization of structure changes in the LBWE

576896    Checks when PSA contains incorrect data for delta requests

449137    BW extraction SD: Extracting documents without changes

382779    Cancellation field in the DataSource maintenance RSA6

216448    BW/SIS: Incorrect update / SD user exit

505700 - LBWE: New update methods as of PI 2002.1

Here you can find the name of the reports (Job control in LBWE)

328181 - Changes to extract structures in Customizing Cockpit

1081287 - Data extraction orders block the upgrade process (problem in p

728687 - Delta queued: No data in RSA7 (How to find the document number

652310 - LBWE: Message MCEX 140 with extract structure change (inconsist

380078 - Records with Status 'NOSEND' in the extraction queue

835466 - Using the repair mode of the hash solution

If you did not load the datas from the delta queue before you changed the extract structure

In case of missing delta records, it is easier to analyse the problem. I

Missing applications in LBWE

387084 - Client-specific tables for logistics extraction

Update of SD Sales Extractor Data for BW (Application 11)

Five Ways to Enhance BI Functionality Using ABAP-- Part I--Data Extraction

Enhance the Extractors (ABAP perpective)

How-to enhance LO-Cockpit DataSources with delta-relevant fields

Colin