Status	Revision in Progress
Owner	CELEDONIO-ext, Arnold MADHOK-ext, Jasleen
Stakeholders

Team Involved	Area
Metawat Sawasdee	Business
Umesh Mudri	Technical
Shivang Dala	Technical
Ravindra Mantri	Functional
Eluard Montineira	Functional

Purpose

The purpose of this document is to define the conversion approach to migrate Vendor Doc Attachments to S/4 HANA.

This allows to associate relevant documents, like contracts or certifications, with specific vendors.

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

BUS2009 - Purchase Requisition Item

BUS2010 - Vendor Quotation Request

BUS2011 - Vendor Quotation

BUS2012 - Purchase Order

BUS2013 - Purchase Scheduling Agreement

BUS2014 - Purchase Contract

BUS2015 - Inbound Delivery

BUS2020 - Vendor Document

BUS2025 - Purchasing Contract

BUS2052 - Purchase Outline Agreement

BUS2105 - Purchase Requisition

BUS2125 - Vendor related Customer Billing Document

BUS2126 - Vendor Billing Document

BUS2126001 Single Vendor Billing Document

BUS3003 Purchasing information

BUS3008 - Vendor Account

etc

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.

Attachment Types

Any type of document can be an attachment, and can be attached when the user creates a PO from the shopping cart.

In most cases this is a PDF type attachment, and includes Invoices, Specs, Emails....

Conversion Scope

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

The data from legacy system includes:

The data from legacy system excludes:

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

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

The data exists. connects to the source and loads the data into . 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 ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

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

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 with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

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 to make the data Target ready:

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
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

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

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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

Configuration

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

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Key Assumptions

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

Change log

Version	Published	Changed By
CURRENT (v. 4)	Feb 11, 2026 10:24	SICONOLFI-ext, Michael
v. 52	Dec 03, 2025 12:42	SICONOLFI-ext, Michael
v. 51	Nov 25, 2025 12:48	SICONOLFI-ext, Michael
v. 50	Nov 25, 2025 10:20	SICONOLFI-ext, Michael
v. 49	Nov 25, 2025 10:10	SICONOLFI-ext, Michael
v. 48	Oct 04, 2025 09:44	MADHOK-ext, Jasleen
v. 47	Oct 03, 2025 10:35	MADHOK-ext, Jasleen
v. 46	Oct 03, 2025 09:59	MADHOK-ext, Jasleen
v. 45	Oct 03, 2025 09:51	MADHOK-ext, Jasleen
v. 44	Oct 03, 2025 09:41	MADHOK-ext, Jasleen

Go to Page History

Mar 18, 2026	Actor	Type	Activity	Version
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:49 pm	v53
From Nov 25, 2025 to Feb 11, 2026
Edited following Approval	SICONOLFI-ext, Michael	Edit	updated the page at 10:10 am
	SICONOLFI-ext, Michael	State	changed state to Edited following Approval at 9:10 am	v49
Nov 24, 2025
Approved	SICONOLFI-ext, Michael	Comment	commented 12:35 pm Yes, depending on the solution. That table links the Vendor to the document.
		Comment	commented 12:34 pm Usually this will need to be a copy to a specified location. Currently we don't know where and what that will be.
		Comment	commented 12:34 pm This will have to be the Syniti team, and the correct access will be provided according.
		Comment	commented 12:31 pm The first criteria is if the Vendor is in scope or is used in an open PO etc. Once the decision is taken regarding the type of allowable documents, then the disallowed documents can be removed form relevancy. Lastly any other rule that functionals/business decide on.
		Comment	commented 12:29 pm Once the functionals define it, it will be added.
Nov 20, 2025
	GUPTA-ext, Priya	Comment	commented 1:50 pm If Syniti team: ECC access will be provisioned??
		Comment	commented 1:00 pm SRGBTBREL-GUID stores the link?
		Comment	commented 12:59 pm how are we planning to transfer into ECM system (need to check)
		Comment	commented 12:57 pm who is entitled to create custom program in ECC?
		Comment	commented 11:21 am where do I find the approved document Type? as Jira task seems to be still open.
		Comment	commented 11:18 am what is the criteria to find old/obsolete vendors?

Workflow history

Space shortcuts

Page tree

CNV-3031 Vendor Doc Attachments

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log