Start of Content Area

Function documentation Uploading Central Settings  Locate the document in its SAP Library structure

Use

The program FOPCB_UPLOAD allows you to upload data from a sequential file into the MIC component and edit the structure setup in the expert mode.

You can upload the following types of data:

·        Organizational hierarchy

·        Account group hierarchy

·        Central process catalog including attributes and P-CO-R (Process – Control Objective – Risk) assignments

·        Management control catalog

The program reads the records from the file and creates a batch input folder that you can import using batch input processing (see Upload).

Integration

This function is built on the program RHALTD00 for transferring data to Organizational Management (BC-BMT-OM) in Organization Plan Mode. For information about RHALTD00, see the documentation on this program. In MIC, the data transfer is available in a simplified form:

·        You can use a file from the client workstation instead of the application server.

·        Organization plan fields such as plan variant or status do not have to be transferred because they are filled automatically during data transfer.

·        You do not have to name the connections between the objects because they are also determined automatically.

Prerequisites

·        Number ranges have been specified for the objects in Customizing for MIC under Structure Setup.

·        The file must exist in CSV format. In this format, the data items within a data record are separated by semi-colons (;). To create such a file, you can proceed as follows:

§         ...

                            a.      Create a file in Microsoft Excel, for example, and format the Excel sheet as text.

                            b.      Enter the data as described below.

                            c.      Save the file as a CSV file, that is, with a file name ending with .csv.

·        The data of a data record has to be arranged in accordance with the FOPC_UPLOAD structure.

Fields of the FOPC_UPLOAD Structure

¡        Object Type: 2 characters

If an object type is only defined by one character, such as using O for the organizational unit, then you also have to enter a space after the character.

¡        Object ID: 8 characters in the customer name space (external number range)

¡        Infotype: 4 characters

¡        Subtype: 4 characters; Only required for certain infotypes

¡        Start of Validity/End of Validity: 8 characters, following the pattern YYYYMMDD

¡        Part specific to infotype: Length varies depending on the infotype

The system reads the first character after the semi-colon. This means that there should be no initial spaces before the actual value itself.

The infotype-specific part must be structured according to the lengths of the components of the structure corresponding to the Infotype. The technical name of the structure consists of the prefix HRI and the number of the infotype, such as HRI1800 for infotype 1800. The components of the structure have to be separated with the exact number of spaces (see also Examples of Lines in Files for Uploading).

Features

You can load the following data into the system:

·        Master data

·        Hierarchies

·        Descriptions

·        Attributes

You can upload master data and descriptions in different languages. Observe the following:

·        The different language versions must be loaded in the same file, otherwise one language version overwrites the other. Create a separate line in the file for each language version. The lines are the same apart from the name or description and the respective single-character language key (E for English, D for German, F for French, and so forth).

·        The language in which you are logged on when you perform the upload must be listed first in the file. The other languages can then follow.

Master Data

Master data is uploaded using infotype 1000 (no subtype). In the infotype-specific part, you enter an abbreviation for an object (12 characters), a name (40 characters), and a language key (1 character).

Possible object types:

·        Organizational unit: O

·        Account group: MA

·        Process group: MG

·        Process: MP

·        Process step: MT

·        Control objective: MO

·        Risk: MR

·        Management control: MM

Hierarchies

Hierarchies are uploaded using infotype 1001 (no subtype). The object type of a data record specifies the superordinate node. Possible object types:

·        Organizational unit: O

·        Account group: MA

·        Process group: MG

·        Process: MP

·        Control objective: MO

·        Management control: MM

In the infotype-specific part, you define the subordinate node of the data record by entering the object type (2 characters) and the object ID (8 characters) of the subordinate object.

The following assignments are possible:

·        Organizational unit to organizational unit

·        Account group to account group

·        Process group to process group

·        Process to process group

·        Process step to process

·        Control objective to process

·        Risk to control objective

·        Management control to management control

For the assignment of process steps to a process, you can additionally specify in the infotype-specific part the sequence of the steps in the process. To denote the sequence of the steps, use 2 characters that can be sorted, such as 01, 02,... or AA, AB, ...

Descriptions

Descriptions are uploaded using infotype 1002 with subtype 1. If several descriptions are permitted, you enter in the infotype-specific part a pointer (32 characters) to the correct description. Then the description itself follows. It has no length restriction. After the description, add the language key (1 character).

Possible object types: See under "Master Data" above

Attributes

The attributes of an object are uploaded using different infotypes numbered between 1800 and 1820.

Possible object types: See under Master Data above

 

Note

For more information on uploading attributes as well as on uploading objects specific to organizational units, see the documentation on the SAP Service Marketplaceunder service.sap.com/rkt ® mySAP Financials Learning Maps ® SAP MIC 1.0 ® Solution Consultant ® Customizing / Power User Transactions ® Creating an Upload File Guide.

 

Example

See Examples of Lines in Files for Uploading

 

 

End of Content Area