This appendix covers the following topics:
Completing this spreadsheet is optional. If you choose not to load parameter values here, you must enter them manually before running the post-upgrade steps. After entering all input data, the Input Data worksheet should be exported as a comma delimited text file, with the name setupdata.txt, and stored in the directory specified in the ECE: Inbound File Path profile option
This spreadsheet contains three worksheets:
Input Data: You can enter the Processing Rules parameter values on this worksheet.
Help: This worksheet describes the structure for the Input Data worksheet and indicates which columns to populate for each level.
Glossary: This worksheet lists all the parameter columns, information about the parameter, and a list of valid values when applicable. You can copy the value to the clipboard and paste it into the desired cell of the Input Data worksheet.
The CARaS environment contains some information relevant to Oracle Release Management not contained in Automotive Extras tables, for trading partners corresponding to Oracle Customers and CARaS Companies corresponding to Oracle Inventory organizations.
You can use the following table as a guide for completing the spreadsheet:
Some values in CARaS might be case-sensitive. Verify the accuracy of the data that you enter in the spreadsheet.
| Source in CARaS | Spreadsheet Column | Notes |
|---|---|---|
| Trading Partner Profiles field TP Code | B - Trading Partner Code | - |
| Abbreviation Cross-References field Destination Code | C - Destination Abbreviation | - |
| Part Master File Maintenance field Customer Part | D - Customer Item | - |
| Company Options field Current Model Year | E - CUM Management Type | If Y, then CUM_BY_DATE_RECORD_ YEAR. |
| Company Options field PO Significance | E - CUM Management Type | If Y, then CUM_BY_PO. |
| Part Destination File | F - CUM Org Level Code | Ship_To_Ship_From, unless otherwise mentioned. Check your CUM setup to verify this value. |
| Use Transfer code CADSTC_MNT, then field CUM Update Type | G - CUM Shipment Rule Code | - |
| Supplier Profiles field Supplier Id 1 | H - Assigned Supplier Code | - |
| Company Options field Enable Firm/Planning Codes | I - Use EDI Ship/Delivery Code? (Y or N) | - |
| Daily/JIP Schedule Options Part Destination File | J - Shipment Delivery Rule Name | - |
| Part Destination File | K - ATS Pre-Horizon Disposition | - |
| Part Destination File | L - ATS Pre-Horizon Cutoff Days | - |
| Cross-Reference 1st Time Interval in Days = “S” | M - Firm Fence - Start N - Firm Fence - End | - |
| Cross-Reference 2nd Time Interval in Days = F | O - Forecast Fence - Start P - Forecast Fence - End | - |
| Part Destination File | Q - Company Code | CARaS Company Code |
| Abbreviation Cross-Reference Order Number | R - Order Number | - |
| Abbreviation Cross-Reference Order Type | S - Order Type | - |
This spreadsheet should be completed with the following structure as a pre-upgrade step.
Customer Level Record
Address Level Record 1
...
Address Level Record n
Customer Item Level Record 1
...
Customer Item Level Record n
| Record Indicator | Column | Description |
|---|---|---|
| 1000 | A | Record Indicator |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | B | Trading Partner Code |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | C | Destination Abbreviation (leave blank for customer level and for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | D | Customer Item (leave blank for customer level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | E | CUM Management Type (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | F | CUM Org Level Code (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | G | CUM Shipment Rule Code (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | H | Assigned Supplier Code (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | I | Use EDI Ship/Delivery Code? (Y or N) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | J | Shipment Delivery Rule Name |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | K | ATS Pre-Horizon Disposition (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | L | ATS Pre-Horizon Cutoff Days (leave blank for customer item level) |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | M | Firm Fence - Start |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | N | Firm Fence - End |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | O | Forecast Fence - Start |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | P | Forecast Fence - End |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | Q | Company Code |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | R | Order Number |
| 2000 | - | - |
| 3000 | - | - |
| 1000 | S | Order Type |
| 2000 | - | - |
| 3000 | - | - |
Specifies the two-digit code for the trading partner to be upgraded.
Specifies the Location code for the Trading Partner to be upgraded.
Specifies the Customer Item Number for the trading partner to be upgraded.
Specifies whether or not CUM accounting is required; if so, define applicable data elements that control accumulation, such as record keeping year, start date, purchase order, and so on. If CUM Management is not enabled, select NO_CUM. Do not enter for Customer Items.
Valid values:
NO_CUM
CUM_BY_PO_ONLY
CUM_BY_DATE_ONLY
CUM_BY_DATE_RECORD_YEAR
CUM_BY_DATE_PO
Specifies the relationship between the supplier and customer business entity for accumulation if CUM Management is enabled. Do not enter for Customer Items.
Valid values:
SHIP_TO_SHIP_FROM
BILL_TO_SHIP_FROM
SHIP_TO_ALL_SHIP_FROMS
INTRMD_SHIP_TO_SHIP_FROM
Specifies the rule for when shipments update the CUM quantity if CUM Management is enabled. If CUM Management is not enabled, leave this field blank. Do not enter for Customer Items.
Valid Values:
AS_OF_CURRENT
AS_OF_PRIOR
AS_OF_YESTERDAY
Specifies the code by which the customer identifies you as supplier in the EDI demand transaction. Do not enter for Customer Items.
Specifies whether the ship delivery code specified on the EDI demand transaction should be used. If Y, then a valid code on the EDI demand transaction will overrule the shipment delivery rule name.
Valid values:
Y
N
Specifies the Shipment Delivery Rule Name to be used to calculate shipment dates in the Demand Processor. This will overrule the ship delivery code specified on the EDI demand transaction if: 1) Use EDI S/D Code? is N, or 2) if the ship delivery code specified on the EDI demand transaction is not in the valid values list.
| Value | Description |
|---|---|
| D | Monday |
| E | Tuesday |
| F | Wednesday |
| G | Thursday |
| H | Friday |
| J | Saturday |
| K | Sunday |
| M | Immediately |
| N | As Directed |
| O | Daily Monday through Friday |
| P | 1/2 Monday and 1/2 Thursday |
| Q | 1/2 Tuesday and 1/2 Thursday |
| R | 1/2 Wednesday and 1/2 Friday |
| S | Once anytime Monday through Friday |
| T | 1/2 Tuesday and 1/2 Friday |
| U | 1/2 Monday and 1/2 Wednesday |
| V | 1/3 Monday, 1/3 Wednesday, 1/3 Friday |
| X | 1/2 by Wednesday, balance by Friday |
| Y | None |
| Z | Mutually Defined |
| SG | Tuesday through Friday |
| SL | Monday, Tuesday and Thursday |
| SP | Monday, Tuesday and Friday |
| SX | Wednesday and Thursday |
| SY | Monday, Wednesday and Thursday |
| SZ | Tuesday, Thursday and Friday |
| ZZ | Mutually Defined/None |
| 13 | Monday |
| 14 | Tuesday |
| 15 | Wednesday |
| 16 | Thursday |
| 17 | Friday |
| 18 | Saturday |
| 19 | Sunday |
| 21 | As Directed |
| 23 | Daily Monday through Friday |
Specifies how the Demand Processor handles past due requirements (unshipped Available To Ship Sales Order demand dated before the system date (formerly Schedule Horizon Start Date)). Do not enter for Customer Items.
Valid values:
REMAIN_ON_FILE
REMAIN_ON_FILE_WITH_RECONCILIATION
CANCEL_AFTER_N_DAYS
CANCEL_ALL
ATS Pre-Horizon Cutoff Days is related to the ATS Pre-Horizon Disposition option of Cancel after N Days. This specifies how many days to keep the past due demand intact. Leave this field blank if you did not select the option of Cancel after N Days. Do not enter for Customer Items.
Specifies the Sales Order Number into which schedule demand will be loaded. Use the same value you specified in CARaS Abbreviation Cross-Reference field Order Number.
Specifies the order type corresponding to the sales order number into which schedule demand will be loaded. Use the same value that you specified in CARaS Abbreviation Cross-Reference field Order Type.
Specifies the starting day of Firm Fence relative to the system date (formerly Schedule Horizon Start Date). Calculate this value based on the CARaS Abbreviation Cross-Reference 1st Time Interval in Days associated with Demand Policy = S.
Specifies the Ending value of Firm Fence relative to the system date (formerly Schedule Horizon Start Date). Calculate this value based on the CARaS Abbreviation Cross-Reference 1st Time Interval in Days associated with Demand Policy = S.
Specifies the starting value of Forecast Fence relative to the system date (formerly Schedule Horizon Start Date). Calculate this value based on the CARaS Abbreviation Cross-Reference 2nd Time Interval in Days associated with Demand Policy = F.
Specifies the ending value of Forecast Fence relative to the system date (formerly Schedule Horizon Start Date). Calculate this value based on the CARaS Abbreviation Cross-Reference 2nd Time Interval in Days associated with Demand Policy = F.
Completing this spreadsheet is optional. However, if you do not enter data at this time, you will not be able to modify it later and it will not be available on shipping documents. After entering all input data, the Input Data worksheet should be exported as a comma delimited text file, with the name carasdata.txt, and stored in the directory specified in the ECE: Inbound File Path profile option
This spreadsheet contains three worksheets:
Input Data: This worksheet is where you enter the turnaround data.
Help: This worksheet describes the structure for the Input Data worksheet and indicates which columns to populate for each level.
Glossary: This worksheet lists all the parameter columns, information about the parameter, and a list of valid values when applicable. You can copy the value to the clipboard and paste it into the desired cell of the Input Data worksheet. If the parameter value can be determined using information from the CARaS environment, this worksheet indicates where it is located in CARaS.
Much of the data for completing this spreadsheet is available by running Release Reports in CARaS, for example, Release History or Firm/Planning Requirements Summary
| Source in CARaS | Spreadsheet Column | Notes |
|---|---|---|
| - | A - Record Indicator | Record Indicator = 1000 |
| Part Destination File | B - Requirement Ext. | - |
| Part Destination File | C - Assembly Line Feed Location | - |
| Part Master File Maintenance field Buyer Code | D - Buyer | - |
| Part Master File Maintenance field Engineering Change Level | E - Customer Item Engineering Change Number | - |
| Part Master File Maintenance field Customer Part | F - Customer Item Number | - |
| Part Destination File | G - Customer Item Reference Number | - |
| - | A - Record Indicator | Record Indicator = 2000 |
| Part Destination File | B - Intermediate Consignee code | - |
| Part Destination File | C - Manufacturer Code | - |
| Part Master File Maintenance field Purchase Order Date | D - Purchase Order Date | - |
| Part Destination File | E - Purchase Order Line Number | - |
| - | A - Record Indicator | Record Indicator = 3000 |
| Part Destination File | B - Release Number | - |
| Part Destination File | C - Returnable Container Part Number | - |
| Part Master File Maintenance field Supplier Id | D - Supplier Code | - |
| Part Master File Maintenance field Our Part Number | E - Supplier Item Number | - |
| Abbreviation Cross-Reference Maintenance field Interchange Id or Group Id | F - Supplier Ship-From code | Either of these values may be correct, depending on the trading partner. |
| Abbreviation Cross-Reference Maintenance field Destination Code | G - Customer Ultimate Destination Code | - |
| Part Destination File | H - Vehicle ID Number | - |
This spreadsheet should be completed with the following structure before running CARaS Turnaround Attributes upgrade.
Record 1
Record Indicator = 1000
Record Indicator = 2000
Record Indicator = 3000
Record 2
...
...
Record N
| Record Indicator | Column | Description |
|---|---|---|
| 1000 | A | Record Indicator = 1000 |
| 2000 | - | Record Indicator = 2000 |
| 3000 | - | Record Indicator = 3000 |
| 1000 | B | Requirement Ext |
| 2000 | - | Intermediate Consignee Code |
| 3000 | - | Release Number |
| 1000 | C | Assembly Line Feed Location |
| 2000 | - | Manufacturer Code |
| 3000 | - | Returnable Container Part Number |
| 1000 | D | Buyer |
| 2000 | - | Purchase Order Date |
| 3000 | - | Supplier Code |
| 1000 | E | Customer Item Engineering Change Number |
| 2000 | - | Purchase Order Line Number |
| 3000 | - | Supplier Item Number |
| 1000 | F | Customer Item Number |
| 2000 | - | |
| 3000 | - | Supplier Ship-From Code |
| 1000 | G | Customer Item Reference Number |
| 2000 | - | |
| 3000 | - | Customer Ultimate Destination Code |
| 1000 | H | - |
| 2000 | - | - |
| 3000 | - | Vehicle ID Number |
Internal value generated for CARaS that is used to link to Oracle demand lines.
The customer's assembly identification, as sent on the LIN segment of the 866 transaction.
The buyer that was sent in on the customer's schedule.
Customer part revision included on schedule.
External customer part number Cross Reference.
Internal references to the item that the customer sent on the schedule
Customer's model number for this sequenced detail.
European requirements
European requirements
European requirements
European requirements
EDI Cross Referencing to Customer Address ID or Supplier ID; where ship-to is different from ultimate destination.
Routing information can be specified for inclusion on customer's Kanban ship labels: facility/dock, location build area, part description, first delivery location, empty container location, beginning Kanban serial, ending Kanban serial, and pickup date/time.
EDI Cross Referencing to Supplier Org ID.
The specific shipping location (such as pool point or airport) corresponding to the shipping location qualifier, as sent by the customer on the TD5 segment.
Customer specified effectivity date of purchase order number included on schedule.
Customer purchase order line number included on schedule.
Customer purchase order Release number included on schedule.
Returnable container specified by customer for item shipment.
Supplier code as specified by the customer on the schedule.
Supplier item number specified by customer.
Customer specified ship from organization code external value.
External ship-to address cross reference.
All error, warning, and informational messages are written to a log file and are also inserted into Oracle Release Management Exceptions table.
A debug file is generated to give additional information. The debug file can be used if problems or issues are encountered while running upgrade. Naming conventions for these files are as follows:
Log File: rlmupg_N.log
Debug File: rlmdebug_upg_N
where N is Oracle Session ID (a unique number generated for each Oracle session). These files will be created under the directory specified by the profile ECE_OUT_FILE_PATH. (If this profile is not set correctly, then debug and log files will not be created.)
When the upgrade runs successfully, a message is printed indicating file names and their locations. This message is displayed as follows:
Debug Information is written to /sqlcom/outbound/rlmdebug_upg_287432. Please check the log file /sqlcom/outbound/rlmupg_287432.log for upgrade messages.
RLM Upgrade completed, see the messages listed above, if any, or check the log file for more information.
This message can be found in log files generated while running adpatch (typically, log files of one of the workers,adwork*.log)
If upgrade terminates with an error, it will end with the following message:
FAILED: file RLMSTUPG.sql on worker 1 for product rlm username RLM.
This message will appear on the screen as well as in the file adpatch.log
If you examine the worker log file (which is adwork01.log, in this example), it will contain a message similar to this:
declare
*
ERROR at line 1:
ORA-06501: PL/SQL: program error
ORA-06512: at line 233
Note: If upgrade fails, a message indicating debug and log file names is not generated, even though the upgrade has generated these files with messages and information pertaining to the upgrade failure. Therefore, you must go to the directory mentioned in the profile ECE_OUT_FILE_PATH and check the latest files generated with the conventions as mentioned above.
Whenever upgrade fails, ADPATCH will halt and can be restarted after resolving the problem.
If any of the validations on file elements fail, the upgrade is stopped with failure. This enables you to correct errors and restart the upgrade from where it stopped.
The upgrade will try to find all possible errors with any of the file elements before stopping with failure.
Defaulting rule: If any of the file elements are Null, the Upgrade will try to default the values from higher-level terms, if applicable, for example if CUM management type is not specified for Ship-to level record, it attempts to default it from customer level record.
Lower level terms are not upgraded/inserted if higher level terms were not upgraded.
Upgrade is rerunable. It will try to update already upgraded records provided that they have not been changed by end users.
The Upgrade will generate a summary message indicating the following:
Number of setup records for which errors were encountered
Number of setup records for which warnings were encountered
Number of customer level setup records upgraded successfully
Number of address level setup records upgraded successfully
Number of customer item level setup records upgraded successfully
There are similar summary messages for Demand Upgrade and CARaS turnaround data upgrade.
Demand upgrade will not upgrade demand lines if the value for any of the mandatory columns are null.