Status
Owner	SICONOLFI-ext, Michael
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to create and migrate Purchase Order Attachments in S/4 HANA.

Attachment Functionality in SAP ECC
- Storage Method: Attachments are typically stored using Generic Object Services (GOS), which allow users to link files to sales documents (via transaction codes like ME21N, ME22N, ME23N).
- Technical Reference: The attachments are managed via the Business Object Repository (BOR) object. The Business Object Repository (BOR) in SAP is a central access point for SAP business object types and their corresponding Business Application Programming Interfaces (BAPIs). It provides an object-oriented view of data and processes within an SAP system and is crucial for integrating SAP with external applications. The BOR also plays a role in SAP Business Workflow, ArchiveLink, and output control. 

Below are the object names with their document types. There could be more that are applicable

BUS2010 - Vendor Quotation request

BUS2011 - Vendor Quotation

BUS2012 - Purchase Order   

BUS2015 - Purchase Requisition

BUS2025 - Purchasing Contract    
BUS2035 - Sales Scheduling Agreement    
BUS2094 - Credit memo request    
BUS2096 - Debit memo request    

Changes in SAP S/4HANA
- Attachments are linked using the Attachment List Service (also used in Fiori apps).

- Technically embedded in the Business Object Processing Framework (BOPF) or handled by Object Page Layout for Fiori views 

- User Experience Enhancements: Drag-and-drop uploads via Fiori.

Conversion Scope

The scope of this document covers the approach for converting active <Data Object> from Legacy Source Systems into S/4HANA following the <Data Object> Master Data Design Standard.

The data from legacy system includes:

1. Relevancy Criteria 1
2. Relevancy Criteria 2
3. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Generic Object Services (GOS) is a functionality that allows users to attach documents, notes, and other objects to business objects like purchase orders. It provides a standard way to manage and access these attachments within various SAP transactions, including those related to purchase orders. 

The following are the key concepts for POs.

• Attachment Management:

  GOS enables users to add attachments (like PDFs, Word documents, etc.) to purchase orders, either directly within the transaction or through a separate DMS (Document Management System) if configured. 

• Viewing Attachments:

  GOS also allows users to view the attachments associated with a specific purchase order. 

• Object Relationships:

  GOS can also show relationships between the purchase order and other objects, like IDocs, workflows, or other related documents. 

• Toolbar/Button:

  The GOS functionality is typically accessed through a toolbar button or a menu option within the purchase order transaction (e.g., ME21N, ME22N, ME23N). 

• Customization:
  In some cases, the GOS button or functionality might need to be activated for specific transactions or user roles using customizing settings. 

• Other:
• GOS also allows for other functions like adding private notes, sending the object to another user, or viewing related workflows. 

The Business Object Repository (BOR) in SAP is a central access point for SAP business object types and their corresponding Business Application Programming Interfaces (BAPIs). It provides an object-oriented view of data and processes within an SAP system and is crucial for integrating SAP with external applications. The BOR also plays a role in SAP Business Workflow, ArchiveLink, and output control. 

Key aspects of the BOR and Purchase Orders:

• Centralized Access:

  The BOR acts as a single point of access for all business objects and their associated BAPIs. 

• Object-Oriented View:

  It provides an object-oriented perspective of business processes, allowing for modular and reusable components. 

• Purchase Order Object:

  The purchase order business object (type BUS2012) is a key object within the BOR, representing purchase order data and operations. 

• BAPIs and Methods:

  BAPIs, which are remote-enabled ABAP function modules, are used to implement the methods of business objects. For example, a BAPI might be used to change a purchase order item or retrieve purchase order details. 

• Attributes and Parameters:

  Business objects have attributes that store object properties (e.g., purchase order number, vendor) and methods use import/export parameters to pass data between different parts of the system. 

• BOR Browser:

  The Business Object Repository Browser (transaction code SWO1) allows users to browse, display, and maintain business objects and their components. 

• Integration:

  The BOR facilitates the integration of SAP with other systems, such as through middleware. 

• Workflow and Other Services:
  The BOR is used in SAP Business Workflow, ArchiveLink, output control, and other generic object services. 

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	Mandatory

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history