Kontakt

Ansicht
Dokumentation

RJKWBZ01 - WBZ Inbound Processing

RJKWBZ01 - WBZ Inbound Processing

rdisp/max_wprun_time - Maximum work process run time   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Description

WBZ inbound processing: import inbound file from WBZ computer center

Requirements

The logical inbound file, computer center and date set up the reference to the physical inbound file: the definition of the logical inbound file must contain the parameters and . When the physical file name is determined, is the computer center and the date from the selection screen.
For information on further options for using parameters in file names, please see the documentation on function module FILE_GET_NAME or on the data element FILEEXTERN.

In the first run, the data is imported from the inbound file to a database table (JKTWBZIN) and read from there in further runs. The contents of this table are deleted again when the data is reorganized by means of report RJKWBZ03. The processing status of a record is noted in a further database table (JKTWBZSTAT).

To prevent obsolete records being imported, you can specify a limit up to which past copy numbers are accepted and correct it to the next copy number for which delivery is viable. If you do not want to do this, you can also have the report accept all copy numbers.

Processing mode:

  1. 'Process all records': Processes all records. The result is displayed in a status list from which you can postprocess individual records in dialog processing.
  2. 'Display status list directly': The records are not processed again and the status list is displayed directly.
  3. 'Test mode: Process ___ records per file': The specified number of records is processed as a test. No database changes take place. If you do not specify a number, the report processes all records as a test.
  4. 'Test mode: Display status list directly': The records are not processed again and the status list is displayed directly. You can postprocess individual records in test mode from this list. No database changes take place.

You can also have the report display the records for a computer center in a separate dialog box. You can access a detail screen for one of these records by double clicking on the record in question. This allows you to view the inbound data for a rough check.

The records to be imported must be in structure RJKWBZ and the return records are also created in this structure.

Authorization check:

  • Authorization object: J_WBZ_IN
  • Authorization: J_WBZ_IN in composite profile J_KVERK_ALL

Output

Errored and corrected records are noted in a database table (JKTWBZOUT) and can be transferred to a confirmation file using report RJKWBZ02.

The list screen displayed contains statistical data on the status of the records processed and provides information on various error and warning situations:

  1. IS-M errors: Errors that are likely not to have originated in the record but to have been caused by incorrect (customizing) settings or distribution data in the System, unsuccessful delivery viability determination or similar error situations. These errors may have to be corrected in the System before WBZ records can be imported properly.
  2. WBZ errors: Errors (red) and corrections (green) that arise when the WBZ records are checked and about which the WBZ company must be informed. Records that lead to errors are rejected and can be corrected manually if necessary (see below) and imported again. Records that have already been corrected automatically exist in the System and can no longer be edited manually.
  3. WBZ warnings: The records referred to were not imported and can only be brought into the System by means of manual postprocessing. The following situations are displayed as a WBZ warning:
    1. Number of copies in record exceeds the warning quantity specified in the customizing settings.
    2. Promotion rebate key is incorrect.

If past copy numbers are only accepted up to certain limits (option on selection screen), the oldest copy number not processed is also displayed in the list.

Manual postprocessing: Double click on an entry in the lists of IS-M errors, WBZ records and WBZ warnings to access an overview listing the records that belong to the appropriate error category. In the overview, you can double click again to access a detail screen on which you can manually edit the inbound record (for records that do not yet exist in the System). You can make changes to the following fields:

  1. Form of address key (field 17)
  2. Name (field 18)
  3. Street (field 21)
  4. Postal code (field 14)
  5. City (field 22)
  6. Address affix and indicator (fields 19 and 20)
  7. Number of copies (field 9)
  8. Promotion rebate key (field 12)

Records that have already led to changes in the System cannot be changed. Instead, you can display the items created in this case.

The details screen contains function buttons that enable you to display data on the computer center or the WBZ company.

The following rules are observed when checking and if applicable changing an inbound record:

  1. Name: The first and last names are only separated if the separator is specified in the name field.
  2. Conversion of address data is controlled by a customizing indicator for the computer center
  3. The correction of a street name in postal shipping, if there is a street directory for the city, is controlled by a further customizing indicator specified for the computer center.
  4. The postal code is normally not changed when the inbound address data is converted.
  5. The text 'P.O. box' must be specified in the street field for P.O. box-related postal codes.
  6. The street field must be blank for major customers (identified by the major customer postal code).
  7. House numbers, house number affixes and storeys are extracted from the street field according to certain rules and transferred to the appropriate IS-M fields.
  8. Second subscriptions do not lead to the creation of a new order but to a new item in the order previously terminated.

Remarks on record fields:

  1. WBZKUNNR + VERTRKENNZ + ABONR: Identify an item uniquely.
  2. WBZTERMIN: Used to determine the time of creation or change.
    In the case of new subscriptions, second subscriptions and changes, the date specifies the time from which the new subscription or the change are valid.
    In the case of terminations, the date specifies the first copy not delivered.





SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 7337 Date: 20240531 Time: 193949     sap01-206 ( 122 ms )