SAP ABAP IMG Activity SIMG_CFMENUOLSDDAT07 (Transfer Data From Sales Documents (Up To 3.1x))

Hierarchy

☛

SAP_APPL (Software Component) Logistics and Accounting
⤷

SD-MD (Application Component) Master Data
⤷

VIO (Package) Introductory Guide to R/3 Organization and Environment

IMG Activity

ID	SIMG_CFMENUOLSDDAT07	Transfer Data From Sales Documents (Up To 3.1x)
Transaction Code	S_ALR_87005818	IMG Activity: SIMG_CFMENUOLSDDAT07
Created on	19981222
Customizing Attributes	SIMG_CFMENUOLSDDAT07	Transfer data from sales documents (up to 3.1x)
Customizing Activity	SIMG_CFMENUOLSDDAT07	Transfer data from sales documents (up to 3.1x)

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUOLSDDAT07

In this menu entry, you start the program for transferring open sales order from an old data processing system to the SAP system.

The following table structures describe the record layout for copying open orders:

BVBAKKOM Header data
BVBPAKOM Partner data
BVBAPKOM Item data and conditions
BVBEPKOM Data from schedule lines

Requirements

Write old data to a sequential file and introduce it to the SAP system.

Actions

Start the program for transferring open orders:

Enter the name or path of the seqential file to which you imported the data from the legacy system.
Enter the indicator for a test run for testing purposes.

Notes on starting the program

When you start the program, enter the name of the file path where the data to be transferred is stored. The following rules apply for the structure of this data:

The data is made up of records which, depending on content, have different structures. Each structure has a name under which it is defined in the Data Dictionary. Copy this name in the first field of the structure (field ....-TBNAM). For more information on how structures are set up, see the Data Dictionary.

Header data and contract head data are transferred using structure BVBAKKOM. Data on document partners is transferred to structure BVBPAKOM. You must enter the item number '00000' for header partners. You can also enter partners at item level by transferring them to the related items with item number.
Item data and conditions are transferred using structure BVBAPKOM. This structure can also be used to transfer an order quantity and a requested delivery date. These are first transferred as schedule lines. In credit/debit memo requests as in contracts, however, all target quantites must be filled in.
Data in other order quantities and dates in the form of schedule lines can be transferred using structure BVBEPKOM.
At the beginning of each data record, the table name must be entered for identification purposes (e.g. BVBAPKOM for item data). Note that, unlike with manual entry, fields must be transferred in part in internal format: Date fields in Format YYYYMMTT, e.g. 19941231.
The date field must be in format YYYYMMDD, for example 19941231.
You must consider data element documentation when working with quantity and value fields. Partner functions must be in internal format: AG = Sold-to party, WE = Ship-to party, RE= Invoice recipient, RG= Payer.
Order types must be in internal format, not in the language-dependent translation, for example 'TA' for Terminauftrag instead of the english translation 'OR' for standard order.
You must enter the period indicator for the requested delivery date in internal format: 1 = day, 2 = week, 3 = month.
Numerical fields and date fields which are not used must be reinitialized with zeros.

The following rules apply for the sequence of the data records:

Each document begins with a header record (BVBAKKOM).
These are followed by the document partners (BVBPAKOM) for the document header.
After that comes the item data and the schedule lines (BVBAPKOM, BVBEPKOM, and BVEDAKOM).

Sample sequence:

BVBAKKOM Header data in first order

BVBPAKOM Partner data

BVBAPKOM Item 1 with a schedule line

BVBAPKOM Item 2 with the first schedule line

BVBEPKOM 2nd schedule line for Item 2

BVBEPKOM 3rd schedule line for Item 2

BVBAPKOM Item 3 with first schedule line

BVBEPKOM 2nd schedule line for Item 3

BVBAPKOM Item 4 with a schedule line

BVBAKKOM Header data in second order

BVBPAKOM ...

BVBPAKOM

BVBAPKOM

BVBAKKOM

BVBPAKOM

BVBAPKOM

The program reads the data and produces sales documents on the basis of it. You can generate a file with test data using Program RVINVBTO.

The program reads the data and generates sales documents.

Output

A log is issued in which it is defined which data can be transferred and which cannot. If data cannot be transferred, this is explained by way of an error message. The old document and item number which were transferred into the data records in the field OLDNR is given for each note in the log. Data which is not transferred must either be entered manually or processed in a later program run (after the input data has been corrected). You can issue sales document data, which has not been transferred, to a file for subsequent processing.

Business Attributes

ASAP Roadmap ID	254	Transfer Data
Mandatory / Optional	2	Optional activity
Critical / Non-Critical	2	Non-critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	SIMG_CFMENUOLSDDAT07	0	HLA0009601	Sales

Maintenance Objects

Maintenance object type

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
IMGDUMMY	D - Dummy object	OV/6	241			Data transfer of open orders

History

Last changed by/on	SAP	19981222
SAP Release Created in

Object Hierarchy

Used by

Advertise Links