Integration of Locations

Use

This section provides you with information as to how the Core Interface (CIF) transfers location master data (plant, customer, vendor, etc.) from the ERP system to the SCM system.

Integration

The ERP master data objects plant, customer, vendor, shipping point, etc. are transferred as locations.

This graphic is explained in the accompanying text.

They differ from each other through their respective location types. The function of a location is therefore dependent upon the location type.

Note that the location type does not belong to the location table key and that this can lead to naming conflicts.

Example Example

If both the vendor and the customer have the same number in the ERP system (for example, customer and vendor 1000 ), you need to rename one of them when entering them into SCM by using the customer exit for the vendor master record (for example, you can rename the vendor S1000 ). If you do not do this, the system is unable to differentiate between the two locations. This is due to the fact that the location type is a key field in table /SAPAPO/LOCMAP but only an attribute in table /SAPAPO/LOC.

End of the example.

Transfer of ERP Master Data to the SCM Location Master

Question	Answer
How is the data transfer from the ERP production plant carried out?	A plant is transferred to the SCM system with the location type 1001 (production plant). For this, all basic settings associated with the plant are transferred: Name, address, time zone, and regional assignment. When a plant is transferred, the transportation zone assigned to the plant in the ERP system is transferred as a separate location of type 1005 in addition to the actual plant location. Additional data in the SCM location:You can maintain the short text for SCM locations in several languages (in contrast to the plant in the ERP system), so that when you log on in a certain language the short text appears in that language.SCM locations generally contain a large number of additional planning parameters for which there is no equivalent in the ERP system. You have to maintain these parameters in the SCM system subsequently. You cannot transfer them from the ERP system.
How is the data transfer from the ERP distribution center carried out (as of SAP R/3 4.0)?	As of SAP R/3 4.0, you can define plants as distribution centers within the framework of the DRP functionality. (DRP: Distribution Resource Planning.) For this, you need to maintain the associated entry in the customizing table in the basic settings of DRP customizing (customizing step Node Type Assignment – Maintain Plant ). If you transfer plants that are defined as distribution centers in the ERP system, these plants are transferred to the SCM system as location type 1002 (distribution center). The transfer of the individual ERP plant settings (in the ERP system, a distribution center is nothing other than a plant) occurs in the same way as for production plants.
How is data transferred from storage location MRP areas of the ERP system (as of SAP R/3 4.5B)?	See Integration of Storage Location MRP Areas .
How is the transfer of customer data from the ERP system carried out?	Customer data is transferred from the ERP system as locations with the type 1010 (customer). When a customer master record is transferred, the transportation zone assigned to a customer in the ERP system is transferred as a separate location of type 1005 in addition to the actual customer location. The missing data that is needed to use the transportation zone for planning in SAP APO has to be entered manually after the transfer. If you work with SAP Advanced Planning and Optimization (SAP APO), the following applies: sales orders are entered in the ERP system and transferred to SAP APO as transaction data. If the customer to whome an ERP sales order is assigned is also to be displayed in SAP APO, the corresponding location must exist in SAP APO. However, a transfer is not mandatory for the pure production planning process.
How is the transfer of vendor data from the ERP system carried out?	Vendors are transferred from the ERP system as locations of the type 1011 (vendor) or type 1020 (carrier) depending on the account group assignment in ERP. (Account group and SCM location type assignments are defined in table CIFVENTYPE in ERP.) Transportation zones are transferred in the same way as customer data.
How is the transfer of shipping point data from the ERP system carried out?	Shipping points are transferred from the ERP system as locations of the type 1003 (shipping point). To change the transfer data of the shipping points prior to sending, the Business Add-In (BadI) CIF_ENHANCED is available.
Which customer exits exist?	ERP function module:CIF_PLANT_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_001 (CIFLOC01) ERP function module:CIF_VENDOR_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_002 (CIFLOC01) ERP function module:CIF_CUSTOMER_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_003 (CIFLOC01) ERP function module:CIF_MRPAREA_LOCATION_MAPERP customer exit:EXIT_SAPLCDC5_001 (CIFLOC02) SAP APO function module:/SAPAPO/CIF_LOC_INBOUNDSAP APO customer exit:EXIT_/SAPAPO/SAPLCIF_LOC_001(APOCF001) SAP APO function module:/SAPAPO/DM_LOCATION_MAINTAINSAP APO customer exit:EXIT_SAPMMDUSER_004 (APOMD004) You can find usage examples and example coding for the customer exits in the relevant documentation.
What BAPIs are there and what is their operation?	Object type: BUS10002BAPI: BAPI_LOCSRVAPS_SAVEMULTI_30ACustomer exit: EXIT_SAPL10002_001 (APOBP003)
How is the transfer of location master data initiated?	There are three possibilities: Initial data transfer For the integration, you must include the relevant locations in an integration model. When you activate the integration model, the locations are sent to the SCM system and created there.A necessary prerequisite for the change transfer and for a series of processes is that the objects are included in an active integration model.You can also repeat the initial data transfer if the integration model is deactivated in the meantime. Change transfer using change pointers You can use ALE change pointers to log changes to customer and vendor master data. They can then be transferred using the program RCPTRAN4 (transaction CFP1) without repeated activation of an integration model. Online transfer of customer and vendor master data using BTE You can also transfer customer and location master data using a Business Transaction Event (BTE). You can set the system so that the transfer of changed and newly created customers and vendors is directly initiated when the master data is updated in the ERP system. When transferring changes, the system always transfers the complete master data record and not just the changed fields. This means that those fields that originate from the ERP system and have been locally changed in the SCM system are overwritten again in the SCM system. You can prevent this information being overwritten in SAP APO by using a customer enhancement. In this case, the system can only automatically recognize that a location has been changed, and transfer the data to SAP APO if you carry out the change directly in the fields of the material master record. Changes to the customizing or profile tables may also mean that you have to transfer the locations again. Changes that only indirectly influence the master record cannot be automatically recognized by the system.
How is the sublocation converted?	There is currently no conversion of the storage location functionality in the SCM system. The Sublocation field exists in the MRP area only.