Functionality
This method is used to update the material master data and movement dataoptimized in the space management program in SAP Retail.
The following data can be transferred to SAP Retail:

• Master data:

Material number, unit of measure, EAN/UPC, material dimensions, sortsequence in shelf, shelf section, horizontal facing, vertical facing,layout module variant, and exclusion indicator. Exclusion means that thematerial is not included in the layout module variant, that is to say,not placed on the shelf.

• Movement data:

Maximum shelf quantity, optimum shelf quantity, presentation quantity.
Import parameters

• Layout module parameter SiteLayoutModule and


• Structure Controls, which contains the following fields:

A plant for which any listing conditions are to be created
The path for the planogram file assigned to the layout module
A plant, if required
The requirement group
An indicator showing whether a listing check is to be run
An indicator showing whether dimensions are to be updated
An indicator showing whether the placement data is to be updated (youshould always set this indicator if a material is to be added to ortaken away from the shelf and/or if the placement data has changed)
The validity dates for listing materials assigned to the layout module.This date is used as the validity date for the layout module version. Ifthe field is empty, the system date is used instead.
An indicator showing whether the update is to be started from this BAPI(=Commit Work)
An indicator showing whether a check against layout module to layout andplant is to be run
A mapping variant. Different mapping variants are defined in thecustomer exit. They can be accessed for every call. For example, onemapping variant can map the movement data and another can cumulate it.
An indicator showing whether the materials concerned are to be listed
An indicator showing whether the layout module version is to be releasedimmediately
A layout module variant to which certain materials are to be assigned
A layout module version. If no version is entered, the 'Valid-from' datecan be used instead to determine the version
An indicator showing whether the 'Valid-from' date is to be used todetermine the version
A document number that links a layout module version to a shelfplanogram file using the document management system
Import and consistency check
The Items table is imported for the optimized material data.
First, additional header data is read for the selection data and checkedfor consistency. The imported material numbers are then compared withthe material numbers in SAP Retail. If a material number in theItems table does not exist in SAP Retail, an additional check isrun to find any materials with the same EAN/UPC. If no such material isfound, then the system deletes the material in question from the table.In this case, the system also records the material in an error log toinform the calling program which material postings led to errors.
In the error log, the system also records cases where a plant in theplant import table did not assign the relevant layout module for theassignment of layout module variants. It also records cases of where theplant does not exist.
Finally, the system checks whether the materials are in the validlisting period or selling period. The start date of listing for thelayout module in structure Controls is used as the check date. Ifmaterials from the import table are not listed or on sale on the date inquestion, an entry is made in the error log for the method.
Updating optimized data
The following data is updated after the checks:

• Date on which the relevant layout module was optimized last


• Update of material dimensions


• Update of layout module version


• Update and assignment of the layout module variants


• Update of material placement data in the layout module and


• Update of the document number

Values <> 0 are also updated, as materials may be assigned to the layoutmodule that were not placed in the planogram, although they are to bekept in the layout module. Material dimensions with values equal to zeroare not updated. To update the optimized stock data, you have to use themethod customer exit from Release 4.5A. As of Release 4.5B, this stockdata can be updated directly without using the customer exit.
Planogram file
A document in the Document Management System links a planogram file witha layout module. You have to make settings in the Customizing for theDocument Management System for this: Definedocument types.
You also need to note that the document type "Layout document" (L01)permits external number assignment. You also make these settings underthe control data - Define document types - inthe detail screen of the document type in the Document Management SystemCustomizing.
In the same place, the indicator in front of "Version Assignment" mustnot be set otherwise different versions will not be able to be createdusing the BAPI.
There are four different ways of updating the document number:

• If the document that is entered in the update BAPI in SAP Retail still
exists, then this document is created.

• If the document that is entered in the update BAPI already exists in SAP
Retail, and the object link to the layout module version as well as theplanogram name and the planogram path have not been changed, then onlythe date on which the document was updated will be changed.

• If the document that is entered in the update BAPI already exists in SAP
Retail, although it is now linked to another layout module version, anew version is created in the version management for the document. Theold version of the document will not be deleted when this happens.

• Finally, if the document that is entered in the update BAPI already
exists in SAP Retail, although the planogram was stored in the spacemanagement program under another path or file name, a new version iscreated. In this case, the old version of the document is also notdeleted.

Notes
If the update indicator is not set in this method, a Commit Work is nottriggered. As a result, a general BAPI BAPI_TRANSACTION_COMMIT iscalled after the method is called. The BAPI triggers the update.
As stated above, consistency checks and dependency checks are run. Thevalidity of customer, layout, and layout module entries is checked andan error message is sent if necessary. Then the customer-layout andlayout-layout module dependencies are also checked.
INCLUDE BAPI_RET
In the listing check, the system checks whether each material is listedand/or can be sold. The check period for the listing check correspondsto the listing period and the selling period. However, a listing checkis only possible if a plant is entered in the control parameter.
Materials are only assigned to a shelf assortment module if theindicator for carrying out listing is selected. Listing conditions arecreated for materials with a horizontal facing > 0 and the shelfassortment modules are assigned to the relevant assortments, if thelayout module on which the version is based has already been assigned toone or more plants.
Before listing can be run, the layout module versions must be released.The can be done in version maintenance in SAP Retail or by using theindicator for immediately releasing versions. If a plant is entered inthe control data, listing conditions are only created for this plant. Inother cases, listing conditions are created for all plants to which thelayout module is assigned.
Directly after data is imported and before the data is updated in SAPRetail, the method has a customer exit which can be used for processingimported data or for imorting and updating additional data.
The length of the document path should not exceed 140 characters.
The layout check verifies if the layout module is assigned to the theplant(s).
The plant control parameter is used for the space management profileassigned to the plant. If no plant is transferred when data is imported,the reference plant for the layout module is used.
The control parameter Requirement groups is not used in the functions ofthe standard system. It is merely an additional option for controllingthe updates for imported space management data.
In addition, the plants to which the selected layout module variant isassigned can be included in the STORES table.
The same applies to updating a layout module variant if a store(customer) was entered in the controls. Its local assortment isalso assigned to the layout module variant.
GLOSSARY:
All important terms are explained briefly below:
Planogram:
Graphical display of a shelf in a space management program.
Layout:
Spatial arrangement of goods in a store or department. A layout is madeup of layout modules and can be assigned to one or more stores.
Layout area:
A layout can be subdivided into layout areas. One layout areacorresponds to exactly one layout module in a layout.
Layout module:
Collection of materials that should be presented together in a store. Alayout module may take up one or more sales shelves. There may differentlayout module versions for one layout module and each is only valid fora certain period of time. Various articles can be assigned to theversions. You can map differences for individual stores compared to theversion that is currently valid using layout module variants.
Layout module version:
Feature of a layout module. The layout module version allocatesmaterials to a layout module for a certain period of time and enablesyou therefore to plan the layout modules. There is at least one layoutmodule version for each layout module. Only one version can ever bevalid at one time.
Layout module variant:
You can determine marginal differences for individual stores compared tothe currently valid version using layout module variants. Additionalmaterials may be contained in the variant or missing from the variantcompared to the current valid version. The current valid version is alsocalled the basic variant. Layout module variants always refer to a basicvariant and only contain, from a technical point of view, the deltawhich is the difference between it and the basic variant.

Further information
For more information, see the documentation forSpace Management in the SAPLibrary.

Description
INCLUDE BAPI_TABLE

Value range
If an error occurs, the following messages are issued:
Messages for input checks:
Type,,Code,,Number,,Message
E,, WB,, 024,, Customer &1 does not exist
E,, WB,, 121,, Layout module &1 does not exist
E,, WB,, 801,, Data for customer & incomplete
E,, WB,, 808,, Layout module &1 is not assigned to customer &2
E,, WB,, 810,, Customer & is not assigned to a layout
E,, WB,, 818,, Customer &1 is not the reference customer forlayout module &2
E,, WB,, 850,, For date &1 no version exists for layout module2
E,, WB,, 871,, Layout module &1 does not have a version &2
Messages on internal errors:
Type,,Code,, Number,, Message
E,, WB,, 005,, No materials are assigned to the selected layoutmodule
E,, WB,, 797,, Field &1, field &2 and field &3 are not selectionfields
E,, WB,, 809,, Import table does not contain any materials
E,, WB,, 813,, No materials listed or on sale
E,, WB,, 820,, Space management profile &1 does not exist
E,, WB,, 822,, Selection variant & for space management does notnot exist
E,, WB,, 823,, No fields in selection variant &1
E,, WB,, 824,, Field &1 is not contained as a return value in selectionvariant &2
E,, WB,, 825,, Neither field name for BV quantity nor for BV value ismaintained
E,, WB,, 829,, Field &1 is not contained as a selection field inselection variant &2
E,, WB,, 836,,Neither field &1 nor field &2 is a selection field inselection variant &3
E,, WB,, 883,, Variant &1 for version &2 of layout module &3 does notexist
E,, W0,, 894,, Select a layout module variant
E,, WB,, 899,, Do not carry out the listing check and the listing atthe same time
If errors occur when material dimensions are updated, the error messagecontains a reference to an error log, which you can display usingtransaction MM90.
If errors occur when listing conditions are created, during the listingcheck, during the assignment of materials to layout module versions, orthe assignment of layout module variants to plants, an error log iscreated, which you can view using transaction WSAD
You can use method BAPI_APPLICATIONLOG_GETDETAIL to displaydetails about the application log.

Description
This structure contains all the necessary control data for posting theoptimized material data from the space management program in SAP. Formore information, see the function module documentation.
INCLUDE BAPI_DATAELEMENT

Description
Grouping of materials for assortment management. The materials areassigned to the layout module in integrated material maintenance.
In addition, Transaction MASS can be used for massassignment of materials to a layout module. The layout module containsall the materials that can be placed in the planogram of the externalspace management program.
INCLUDE BAPI_KEYFIELD

Value range
The system checks the layout module to customer and layout module tolayout assignments, and records incorrect entries in the messageLayout module is not assigned to customer.

Description
This structure is used to select and import header and item data.


• To prepare additional header data for import, you must create your
additional fields in structure BAPI_TE_HEAD_DATA, and fill thistable referring to the structure. A required entry parameter in thestructure is the layout module.
To provide additional item data for the import, you must create youradditional fields in structure BAPI_TE_ITEMS and fill this tablereferring to the structure. Required entry parameters for the structureare the material and unit of measure.
This table supplies data for the customer exit of the method.
INCLUDE BAPI_DATAELEMENT

Description
This table contains all the material data assigned to the layout moduleand optimized in the space management program.
INCLUDE BAPI_DATAELEMENT
You must enter either the material number or the EAN/UPC to be able toupdate the data.

Description
Import table for the assignment of layout module variants to theindividual plants. The layout module variant is assigned to each ofthese plants. In this process, the system checks whether the layoutmodule in question is itself assigned to the plant.