10 Spreadsheet Upload External v35 - IBM€¦ · 10 Spreadsheet Upload External_v35.doc 16/09/2003 Page 4 of 15 General Spreadsheet Upload Overview A Spreadsheet is a document with

Spreadsheet Upload

External Release 3.5

Version 01

IBM UserIBM User

RSC@ External User Guide Rel. 3.5 ______________________________________________________________

______________________________________________________________ 10 Spreadsheet Upload External_v35.doc 16/09/2003

Page 2 of 15

Table of Contents

TABLE OF CONTENTS ......................................................................................2 PREFACE .......................................................................................................3

Document Structure...................................................................................................................3 GENERAL SPREADSHEET UPLOAD OVERVIEW ...................................................4

Spreadsheet formats ..................................................................................................................6 Data Types ................................................................................................................................6 Example ....................................................................................................................................7

SPREADSHEET UPLOAD.................................................................................10 Supply/Commit ........................................................................................................................ 10

Basic flow of the function.................................................................................................................. 10 Menu Path......................................................................................................................................... 10 Transaction Path................................................................................................................................ 10 Supply/Commit Spreadsheet upload................................................................................................... 11 Special Feature: Download Commitment to Upload............................................................................ 12 Forecast Commit spreadsheet format.................................................................................................. 14 Sample file (Supply/Commit data created in an Excel-sheet):.............................................................. 15



Page 3 of 15

Preface This manual provides an introduction to the Spreadsheet Upload functionality of the IBM Replenishment Supply Collaboration Application Document Structure This manual is made up of multiple documents to facilitate printing and allow the user to focus on the features they are interested in. All documents are in Microsoft Word’97 format. The following table lists the available documents and their contents: Document Contents 01 General Web External V35 General Introduction 02 General Functionality External V35 General Functionality 03 Forecast External V35 Forecast 04 Refill Cycle External V35 Refill Cycle 05 Inventory External V35 Inventory 06 Pull Cycle External V35 Pull Cycle 07 Bypass Cycle External V35 Bypass Cycle 08 System External V35 System 09 Help External V35 Help 10 Spreadsheet Upload External V35 Spreadsheet Upload 11 Menu Structure External V35 Menu Structure



Page 4 of 15

General Spreadsheet Upload Overview A Spreadsheet is a document with information in a strictly defined format. Because of this, Spreadsheet Upload is a very sensitive operation. Although uploading a spreadsheet is not a main menu item (it is accessed from the “system -> administration menu”), – it is explained separately and in detail in this user manual because of its importance. Within the Refill cycle, information is transferred between suppliers and IBM plants. RSC@ is an essential component in the efficient management of this process. Spreadsheet upload is the key information source for Demand and Forecast, Supply and Commitment for both internal and external users. The flow of information can either be generated at the Back-End by MQ series (ERP-system, e.g. SAP) or at the Front-End by Spreadsheet. It can be a “Load” (data-creation) or an “Update” (data-change) at every step of the RSC process.



Page 5 of 15

Within the RSC@ Application the user can access one of the key functions related to Spreadsheet Upload (System -> Administration -> Monitoring -> Interfaces -> Spreadsheet Upload): • Upload Forecast Supply/Commit

Suppliers usually send their response to FC data as Supply or Commitment. This response is sent to key users in IBM plants who process the information and are responsible for the “external” upload into the system.

Supply and Commitment are joined under the Forecast Supply/Commit function because the structure and the content of their spreadsheets are similar.



Page 6 of 15

Spreadsheet formats All spreadsheet files should be of *.CSV format. Negative numbers are not allowed to pass from any of the data feeds into RSC@. There are two sub-formats that are supported by RSC@ 3.5:

1. Semicolon-separated spreadsheet: For semicolon-separated spreadsheets, all separators except the last one in each line are semicolons (;). The last separator in each line is normally “end-of-line”. If the last data item is an empty string, the last separator is a combination of semicolon (;) and end-of-line.

2. Comma-separated spreadsheet: For comma-separated spreadsheets,

all separators except the last one in each line are commas (,). The last separator in each line is normally “end-of-line”. If the last data item is an empty string, the last separator is a combination of comma (,) and end-of-line.

The spreadsheet format for FC Supply and FC Commit differ in both the number of items and their type. Detailed specifications are provided under the related sub-menu. Data Types Each item in the data line must be a specific data type. The five different data types are: String, Integer, Double, Boolean and Date. 2.1. String data type The item that has data type ‘String’ can be any sequence of characters. The length must be less than or equal to the predefined maximum length for the item. 2.2. Integer data type The item which has data type ‘Integer’ can be any integer number from -2 147 483 648 to 2 147 483 647. 2.3. Double data type The item that has data type ‘Double’ can be any floating-point number from -1.79769E+308 to -2.225E-307, or from 2.225E-307 to 1.79769E+308 2.4. Boolean data type The item which has data type ‘Boolean’ can be either ‘no’ or ‘yes’.



Page 7 of 15

2.5. Date data type The item that has data type ‘Date’ must have following format: ‘dd.mm.yyyy’, where ‘dd’ is a two-digit integer that identifies the day, ‘mm’ is a two-digit integer that identifies the month, and ‘yyyy’ is a four-digit integer that identifies the year. The combination of ‘dd’, ‘mm’, ‘yyyy’ should correspond to a valid date. Example This is an example of a valid spreadsheet (Forecast data created in an Excel-sheet):

The Operation mode is an update (UPDT). The Forecast type is in this case a Forecast. The Manufacturing Line is located in Vac (HG11). The Material number is listed in the 5th column (->00k0040). HOW TO – practical advise on how to create and convert a spreadsheet Whenever a spreadsheet is created in Excel, 1-2-3 or a similar program, it is important to follow a few rules securing the transition of a spreadsheet into the correct format and a successful upload procedure into RSC@. 0. Prerequisite: You have filled all relevant rows and columns with the appropriate information in your spreadsheet (Excel/1-2-3) 1. Mark all filled cells

2. Save file as .csv (within 1-2-3 you need to toggle the box “save selected range only”)



Page 8 of 15

3. Open a text editor such as “EditPlus” and select the file you have saved.

4. Check the number of tokens (correct numbers of commas?) – evaluate your input once more (e.g. correct mfg-line_rsc-line combination; FC version OK?; FC Load Type OK?; …)



Page 9 of 15

5. Save your changes.



Page 10 of 15

Spreadsheet Upload

Supply/Commit Basic flow of the function

Menu Path The function can either be reached • per menu path

(System -> Administration -> Monitoring -> Interfaces -> Spreadsheet Upload -> Supply/Commit)

Transaction Path • or by choosing Transaction code MU03 and pressing the GO Button



Page 11 of 15

Supply/Commit Spreadsheet upload The selection screen for “Forecast Supply/Commit” will pop up.

On this screen the user can define his selection criteria. Manufacturing Line identifies the plant-line in which the file is loaded Value’s Separator: specifies whether the Spreadsheet is comma or

semicolon separated File name: specifies the path to the file in the user’s hard disk. “Browse” opens a file selector dialog to help find the designated file:



Page 12 of 15

After pressing the Button the user will get the following message.

The User will receive an email with the success message and a summary of the good and the bad records. After pressing the Button the user will be linked to the selection screen. Special Feature: Download Commitment to Upload A new feature with RSC@ 3.5 release offers the possibility to download commitment data in the format to upload it right away as spreadsheet. Following steps need to be performed:

1. Choose transaction code SU03 (for Supply) or CM03 (for Commitment); alternatively follow the menu path RSCA -> Forecast -> Supply -> Display or RSCA -> Forecast -> Commit -> Display



Page 13 of 15

2. Select the Transaction Type “Download = SUP Upload” and press the Continue button. 3. Save the file to a folder of your choice. 4. Open the file into a 1-2-3 or Excel-Spreadsheet 5. Input the committed quantities

6. Save file as .csv (comma-separated SS). Now the file is ready to be uploaded as described above.



Page 14 of 15

Forecast Commit spreadsheet format Functionality: Uploading the Forecast Supply/Commit records from the External System into RSC@ via Spreadsheet. Name: FC_SSU_IN Granularity: One per Mfg. line – FC type combination Structure: The amount of items (ItemsNum) in one line of Forecast commit spreadsheet equals to 15. The description and sequence of items in data line of forecast commit spreadsheet is presented in the Table 5. Table: Forecast Commit spreadsheet data line items description and sequence (Completely new to match the download)

Item Item description Item type Example Is mandatory Max. length

1 Mfg. Line Code* CHAR RTP Yes 20

2 RFU*** CHAR PCDRTP No 20

3 Part number* CHAR 06P5178 Yes 20

4 Supplier part number CHAR S306P5178 No 20

5 Part description*** CHAR Modem No 40

6 Supplier number* CHAR 825 Yes 10

7 PO number*** CHAR A1410 No 10

8 Total PO quantity*** Integer 55 No 9

9 Delivery date*** Date 21.10.2001 No 10

10 Supplier scheduled qty*** Integer 55 No 9

11 Commitment date* Date EMPTY Yes 10

12 Commitment quantity* Integer EMPTY Yes 9

13 Commitment comment** CHAR EMPTY No 200

14 Forecast version number* CHAR 1111101451 Yes 10

15 Forecast type* CHAR UC DM or FC Yes 2

16 Forecast order type CHAR PO Yes 3

17 RFU*** CHAR EMPTY Yes 4

18 Sub Geo CHAR AJ No 10

* Mandatory **Not validated by RSC, can send any values, import into RSC@ *** Not validated by RSC, can send any values, NO import into RSC@ There is only one operation mode for the forecast commit spreadsheet: “UPDT”. The operation consists of update of commitments for the current forecast identified by “Mfg. Line code”, -”Forecast type”, “Part number” and “Supplier number” data items combined with the spreadsheet data. If some data lines are not processed because they do not comply with the restrictions on data, they are skipped but other data lines are processed.



Page 15 of 15

Important: The “Supplier part number”, “Part description”, “PO Number” and “Forecast order type” data items do not make any updates to existing forecast records. The last three of these data items are not used at all. The following are restrictions on forecast commit spreadsheet data items across all data lines: 1. Values in “Forecast type”, “Mfg. Line code”, “Forecast version number” data items should be the same across all data lines. The following are restrictions on forecast commit spreadsheet data items which belong to one data line: 1. The “Operation mode” data item must be either “LOAD” or “UPDT”. The operation mode is always “UPDATE”; 2. The “Forecast type” data item must be either “UC” (for Demand) or “FC” (for Forecast); 3. The “ERP code” data item must be the same as the one, which is defined for manufacturing line “Mfg. Line code”; 4. The combination of “Mfg. Line code”, “Part number” and “Supplier number” data items (if “Part number” data item is not empty) or the (combination of “Mfg. Line code”, “Supplier part number” and “Supplier number” data items (if “Part number” data item is empty) must exist in the system Material master record; 5. One of the data items “Part number” and “Supplier part number” must not be empty; 6. The number which is made from last n characters of “Forecast version number” data item (where n is a forecast version length for the manufacturing line “Mfg. Line code”) must be the same as the number which is made from last n characters of forecast version number of current forecast for “Mfg. Line code”-”Forecast type” combination; 7. The numerical value of “Commitment quantity” data item must be greater than or equal to zero. Sample file (Supply/Commit data created in an Excel-sheet):

Documents

10 Spreadsheet Upload External v35 - IBM€¦ · 10 Spreadsheet Upload External_v35.doc 16/09/2003 Page 4 of 15 General Spreadsheet Upload Overview A Spreadsheet is a document with