SAP EWM Delivery integration processing in SAP S4 HANA
- 3. Creation of the delivery document is normally performed in the ERP system, but the origin of a delivery document can be in the EWM system. For example, a manual inbound delivery can be created in EWM. Changes to delivery documents can originate in either the ERP system or in the EWM system. A changed ASN from a vendor can cause inbound delivery changes to be copied from the ERP system to the EWM system. A pick denial in an EWM can result in delivery changes from the EWM system to the ERP system. Delivery splits in EWM can also result in delivery messaging between the EWM system and the ERP system. Sending confirmations of deliveries from EWM for follow-on functions in SAP ERP (for example, goods receipt, goods issue, confirmation before goods issue for invoicing before goods issue) is another example of delivery document data exchange between the EWM system and the ERP system. For these delivery data exchanges, delivery integration settings must exist in the EWM system. SAP provides a set of standard settings for the common SAP delivery documents. The foundation of these settings exist in a table used to translate/cross reference the ERP delivery document types to EWM delivery document types.
- 4. In addition to mapping of the delivery document types, the integration between the ERP system(s) and the EWM system includes a mapping table that maps the ERP Delivery item categories to the EWM Item Type code. In each of the EWM integration tables, the Business System field is present to allow mapping of the document types and item categories based on the specific system from which these objects are present.
- 5. General EWM Delivery Document Control • In general, a document contains all of the data related to a business transaction in a business process. • Every document provides various actions that are used to control the individual subsequent processes. The execution of the actions depends on the settings in the Post Processing Framework (PPF). • A document comprises a document header and any number of document items.
- 6. Contained in the delivery header is general data information and data that is relevant for inbound and outbound delivery documents, posting changes and internal stock transfers. This data is valid for the entire document. This data includes: – Goods receiving office or shipping office – Scheduling data (for example, shipping or delivery date) – Weights and volumes for the complete delivery – Ship-from party, sold-to party and goods recipient numbers The document header is defined in the EWM system by a combination of the document category and the document type codes. The document category classifies the different documents that can be processed by the system in delivery processing. Document category codes are predefined in the EWM system and cannot be changed.
- 7. The following are document categories that exist in delivery processing:
- 8. Assigned to the document category are configuration attributes that define the fundamental EWM process (Inbound, Outbound, Posting Change and Stock Transfer) and process sequence of the document The EWM document type classifies a document with regard to the complete delivery process. The document type defines the primary business use of the document. Shown below are examples of EWM document types:
- 9. Shown in the table below are the major EWM delivery documents and their respective document type and document category codes.
- 10. Each combination of document type and document category in the table above represents a document in a EWM business process. You can create your own document types in the respective process configuration (goods receipt, goods issue, stock transfers and posting changes). There are delivery relevant customizing settings in the major business process (goods receipt, goods issue and internal warehouse processes) for each delivery document. These settings are used to control the processing of the delivery document in the business process.
- 11. Document Item In the delivery document items are contained the information related to an individual products within the delivery. Listed below are examples of item related information: – Product/material number – Delivery quantity – Weight and volume for item – Location-related information such as goods receiving point or unloading point. – Dates such as goods receipt or picking date. – Tolerances for over and under delivery quantities. Each delivery document item is identified by an item type, the document type of the delivery document in which it appears and the item category code. The item category classifies the delivery item into its basic use
- 12. Item category codes are defined by SAP and cannot be changed. Delivery item types classifies the items for a document type with regard to the complete business process. The item type defines the business characteristics of the item in a delivery document. You can configure your own item types to represent delivery items having business characteristics that are different from the standard
- 13. Service Profiles In EWM the delivery documents represent various delivery processes in the system. In delivery processing a series of services and functions are used to configure how the documents are to be processed and to define the business features of the documents that provides the functions that are required in the business processes. Service profiles are used to define how the document types and item types are processed within EWM as well as their business scope. Two types of system profiles are defined within EWM: – System profiles – Customer profiles System profiles are not configurable and are defined as part of the standard EWM system. The system profiles contain configuration settings that are used as the default options in the various delivery document processes. These settings cannot be changed. Internally, the system profiles are linked to the document categories for profiles related to header settings and to the item categories for profile settings related to document items. To configure your own business processes you must create customer profiles. Customer profiles are always linked to the corresponding system profile. SAP has also created a set of predefined customer profiles for the standard delivery processes.
- 14. The graphic also illustrates the basic structure of the service profile tables. In each table that contains the customer profile settings for a particular function the customer profile must be assigned to the standard system profile for the function. The customer profiles are assigned to the delivery document types and item types in their respective process configuration: goods receipt, goods issue, internal warehouse processes
- 15. There area variety of service profiles that are used to control various delivery functions in EWM. The graphic below shows the delivery document functions controlled by service profiles.
- 16. Number range assignment for EWM delivery documents are configured in the General Settings and does not require the use of a service profile. Each of the service profiles is used to control a particular delivery document function. • Status management • Quantity offsetting • Text management • Field Control • Incompleteness check • Actions for Post Processing Framework (PPF) • Partner processing • Process management and control • Reference document types • Date types
- 17. Status management is used to control business transactions used to process a delivery document by assigning one or more statuses to the document. A status can be used to allow or prohibit a business transaction or it can have no affect at all. Status profiles are assigned to delivery types and item types. A status profiles contains status types that describe a partial view or process in the processing of a delivery document such as goods receipt status, unloading status or putaway status. Each status type has one or more status values assigned to it that represent the valid values that the status type can take on such as Yes/No, .Not started/In Process/Completed. The status value can be used to allow or disallow a business transaction and a business transaction can set a new status value.
- 18. In delivery processing, quantity offsetting is used to calculate the open quantities for a document, or to calculate the relevant quantities such as requested quantity and reduced quantity. Quantity offsetting is executed at the item level of a delivery document. To execute quantity offsetting automatically, a quantity offsetting profile is used. The quantity offsetting profile contains the quantity calculation and quantity offsetting rules to be used by the quantity offsetting to calculate the desired quantities. The quantity offsetting profile is assigned to the delivery document type and the delivery document item type.
- 19. Text management is the EWM function that allows texts to be received via delivery documents from the SAP ERP system and processed within the EWM delivery documents. New texts can also be created and saved within EWM delivery documents. Text management supports texts at the delivery header and item level. In EWM you can create, display, change or delete texts within delivery documents. In EWM customizing, text types representing particular text notes such as “shipping instructions” and “preferred carrier” are defined. Text profiles are created to group desired text types for a particular delivery header or item. Within the text profile are the access sequences for each text type. The access sequence is the object used to indicate the source of the text. Text profiles used to specify texts for delivery headers are assigned to the document type; whereas, text profiles used for delivery item texts are assigned to the item type.
- 20. As a system function, field control determines which fields are displayed and changed during delivery document processing. Delivery documents contain a multitude of fields that contain the data used and required in delivery processing. The fields that appear in the delivery header and item structures are determined and controlled by the field control function. Field control is also dependent on the status management function. During the delivery process, the EWM system controls which fields can be display and changed based on the status of the document and item type. Field control is used by delivery processing during the following events: • During the creation of a document or document item • When switching between display mode and change mode • After data is changed in a document The assignment to the delivery document type or item type is made possible via the field control profile. A field control profile contains all the allowed fields and their attributes for a particular document or item type. Every field control profile is assigned to a system profile.
- 21. The settings for an incompletion check is saved in an incompleteness profile. Depending on where the incompleteness check is to be used, the profile is assigned to the document or item type. Pre-configured incompleteness profiles and setting are delivered by SAP for the standard processes in delivery processing.
- 22. Message/output control for delivery processing uses the Post Processing Framework (PPF). The PPF is a Basis component that generates actions from the data of an application according to an action definition (e.g. the printing of a delivery note). The actions are processed at a certain point in time. The PPF provides the tools for the scheduling, starting and monitoring of actions. In addition to printing-related actions, Actions can include: • Activating delivery documents such as inbound delivery notification or outbound delivery requests. • Posting goods issue or receipt Actions are saved in an action profile. The action profile is linked to the document type.
- 23. Partner processing is the system function that provides the ability to maintain partner information in the header and/or item data in EWM delivery documents. Partner processing configuration begins with the creation of partner roles. The partner role is used to represent a role or a function in the business process. Examples of possible partner roles are: supplier, receiving office, ship-to recipient, warehouse. Partner roles are identified by a six-character key, a description and a role category. The role category code defines the nature and use of the partner identified by the partner role. The following role types are available: • Business partner • Location • Organizational unit Partner roles are assigned to partner profiles. The partner profiles are assigned to the document types and item types where they are used. Predefined partner profiles have been created by SAP for the standard EWM delivery documents. These profiles are the partner processing system profiles and cannot be changed. In these profiles SAP has defined the partner profiles with mandatory and optional partner roles.
- 24. To control whether certain processes or functions are permissible for a delivery type or item, EWM uses the Process Management and Control function. The following process indicators can be set for the delivery header control: • Manual creation - controls whether a document can be created manually in EWM • Preceding document - allows reference to a preceding document • Production - allows processes for production such as kit-to-stock, goods receipt from production. • Scrapping - allows subprocesses for scrapping • Pickup - allows process for sales without transportation processing • Invoice before goods issue - allows an invoice to be created before the goods issue • Correction delivery - allows posting of differences to the stock of the differences to be cleared using a correction delivery document. At the item level the following process indicators can be set: • Create manually - an item can be created manually in a delivery document without reference to a line item in a preceding document. • Invoice before GI - allows the billing of a line item before its goods issue posting. Like other system functions, process management and control contains SAP pre-created system profiles for the standard delivery categories and item categories.
- 25. In the Reference documents service profile configuration, the allowed preceding document references are configured. Within the system and customer profiles the permitted reference documents are defined using reference document category codes. The reference document customer/system profiles are assigned to the document categories where they will be used. SAP provides a pre-configured set of profiles for the standard EWM delivery document and item categories.
- 26. Various dates related to delivery processing can be, and are, configured for EWM delivery document processing using the Date Types system function. The dates that are supported by the system are defined as date types. It should be noted that the time of day always accompanies the day of the date. The supported date types are determined by the EWM application functions. As a rule, the EWM date types should match the date types defined in Configurable Process Scheduling. Examples of date types include: delivery date, goods issue date, start of loading, end of loading, and pick/pack start. Date profiles are pre-configured in the EWM system for all of the standard delivery types and item types. Each date profile is assigned to a system profile. Contained within the date profile are the date types that are to be used in the corresponding delivery type or item type to which the profile is assigned. If you do not define a date profile for a document type or an item type, the settings for the corresponding document or item category from the system profile are used automatically.
- 27. Service Profile Assignment Within each EWM business process, the delivery document types and item types are configured with their general and service profile settings
- 28. Delivery Document Determination When EWM delivery documents are created as successor documents, or manually without reference to a document (if permitted), the system uses determination tables to assign the document type and item types to the new delivery document that is being created. Delivery document type and item type determination tables are present in the business process configuration activities in the IMG: – Goods Receipt – Goods Issue – Internal Warehouse Processes - this includes posting changes and internal – stock transfers
- 29. To determine an item type for a delivery item, the system uses a group of fields as illustrated in the following figure
- 30. Define Document Types for Inbound Delivery Process
- 31. Define Item Types for Inbound Delivery Process
- 32. Define Allowed Item Types in Inbound Delivery Process
- 33. Define No. Range Intervals for Inbound Deliveries and Outbound Del. Orders Define Number Range Intervals for Outbound Deliveries Define Number Range for Posting Changes and Stock Transfers
- 34. Map Document Types from ERP System to EWM
- 35. Map Item Types from ERP System to EWM Map Item Types from ERP System to EWM
- 36. Map Date Types from ERP System to EWM Map Partner Roles from ERP System to EWM
- 37. Define Document Type Determination for Inbound Delivery Process
- 38. Define Item Type Determination for Inbound Delivery Process
- 40. Also Discuss the following: • Quantity Offsetting • Text Management • Field Control • Incompleteness Check • Actions • Partner Processing • Reference Documents • Dates/Times • Process Management and Control
- 41. Thank You Next Topic is Inbound Process