Entering content frameFunction documentation SRS_PDC_SO_STRUCTURE Interface Locate the document in its SAP Library structure

Use

This provides PDC devices with information on the assortment list structure.

RFC module SRS_PDC_SO_STRUCTURE is used as an RFC outbound interface. The module is called up and provided with data by program R_SRS_PDC_ASSORT_STRUCT_OUT.

Integration

Article data is transferred by RFC module SRS_PDC_SO_OUTBOUND to the PDC devices for store requirements planning. The article data is grouped. The type of grouping is determined by RFC module SRS_PDC_SO_STRUCTURE.

If you are using the SAP Business Connector for the data transfer, there are specially developed help programs that use field FILE_NAME to generate files in XML format. All the file names that were created by RFC module SRS_PDC_SO_OUTBOUND are included in table GROUP. RFC module SRS_PDC_SO_OUTBOUND issues one file for each row in table GROUP.

For an exact description of the interface’s data structure, see the SAP Interface Repository, which all users can access.

Prerequisites

You must have either a full or a mixed version of the assortment list to use RFC module SRS_PDC_SO_STRUCTURE.

To be able to use the module, you have to define an RFC destination in SAP R/3 that is assigned to your target system. The target system may be a SAP Business Connector or a non-SAP system (for example, a PDC server). You must enter partner and port profiles for the RFC destination.

You make settings in Customizing for the assortment list profile to group the article data. This is controlled in the assortment list profile by the field Sorting Procedure. The article data is grouped in two- or three-level hierarchies depending on the sorting procedure. The highest hierarchy level is always the assortment list type. All assortment list types and their names are transferred to table HEAD. Table GROUP provides information on groupings under the assortment list types. Field ASSORTLIST_TYPE links tables HEAD and GROUP. The groupings described in table GROUP can be summarized (for example, into departments) – again depending on the sorting procedure – and describe the one to two hierarchy levels below the assortment list type.

The following sorting procedures are available:

1: Assortment list type, department, layout area

2: Assortment list type, layout area

3: Assortment list type, vendor, vendor subrange

4: Assortment list type, vendor, merchandise category

5: Assortment list type, department, merchandise category

6: Assortment list type, merchandise category

9: Assortment list type, others (user exit)

For sorting procedure 4, article data is grouped according to vendors as well as being cumulated according to merchandise categories.

Features

RFC module SRS_PDC_SO_STRUCTURE formats data for grouping assortment lists.

Field GROUP_KEY can identify every assortment list group with a unique key.

A name is assigned to the group in field GROUP_TEXT depending on the sorting procedure. This name is derived from the assortment list type and from additional group-specific field contents. The name is used as a group description that is displayed on the PDC device.

The data with which you are provided by RFC module SRS_PDC_SO_OUTBOUND may be too comprehensive for you to process it efficiently on the PDC device. For this reason, RFC module SRS_PDC_SO_STRUCTURE provides you with information about all the existing assortment list groups in your store. This way you can save all your store-specific information on the assortment list structure on the PDC device and the user can only access article data on assortment list groups that are required for his or her work.

In outbound processing, any errors that occur are logged in the application log (transaction SLG1) under object W_SRS and subobject PDC_STRUCT.

Activities

You can execute interface SRS_PDC_SO_STRUCTURE using program R_SRS_PDC_ASSORT_STRUCT_OUT. You only need to call the program at the beginning or when changes have been made to the assortment list structure.

 

 

Leaving content frame