This appendix covers the following topics:
The Available-To-Promise (ATP) API is a public API that can be used to calculate the material and resource availability across a supply chain. The API accepts information about an item or group of items, checks the availability for the items and returns the availability picture for the items.
The specification of the ATP API follows:
p_session_id | IN OUT | NUMBER, |
p_atp_rec | IN | MRP_ATP_PUB.ATP_Rec_Typ, |
x_atp_rec | OUT NOCOPY | MRP_ATP_PUB.ATP_Rec_Typ, |
x_atp_supply_demand | OUT NOCOPY | MRP_ATP_PUB.ATP_Supply_Demand_Typ, |
x_atp_period | OUT NOCOPY | MRP_ATP_PUB.ATP_Period_Typ, |
x_atp_details | OUT NOCOPY | MRP_ATP_PUB.ATP_Details_Typ, |
x_return_status | OUT | VARCHAR2, |
x_msg_data | OUT | VARCHAR2, |
x_msg_count | OUT | NUMBER |
Where:
p_session_id: This is the session identifier of the user transaction. The session id is passed to ATP API from the calling module. Call msc_atp_global.get_atp_session_id(.....) API; this will guarantee that session_id remains unique through various calls.
p_atp_rec: This record of tables contains information about items for which resource and material availability check needs to be done. This record is explained in detail in another section.
x_atp_rec: This record of table contains resource and material availability information generated by ATP for items passed to ATP API in p_atp_rec. This record is explained in detail in another section.
x_atp_supply_demand: This record of tables contains information about supplies and demands ATP considered to check the availability. This record is explained in detail later in another section.
x_atp_period: This record of tables contains net supply and demand picture for the items for the whole time horizon during which availability is checked. This record is explained in detail later in the document.
x_atp_details: This record of tables is not used by ATP.
x_return_status: This variable contains the overall status of ATP check. There are three possible value for this variable:
FND_API.G_RET_STS_SUCCESS: The return value is 'S'. It means ATP request was successful.
FND_API.G_RET_STS_ERROR: The return value is 'E'. It means that some error occurred during ATP check.
FND_API.G_RET_STS_UNEXP_ERROR; The return value is 'U'. It means that an unexpected error occurred during ATP check.
x_msg_data: This variable is not used by ATP.
x_msg_count: This variable is not used by ATP.
The following nested tables are used for defining data types of members in a record:
Col. 1 | Col. 2 | Col. 3 | Col. 4 | Col. 5 | Col. 6 |
---|---|---|---|---|---|
TYPE | number_arr | IS | TABLE | of | number |
TYPE | char1_arr | IS | TABLE | of | varchar2(1) |
TYPE | char3_arr | IS | TABLE | of | varchar2(3Available-To-Promise |
TYPE | char7_arr | IS | TABLE | of | varchar2(7Available-To-Promise |
TYPE | char10_arr | IS | TABLE | of | varchar2(10Available-To-Promise |
TYPE | char15_arr | IS | TABLE | of | varchar2(15Available-To-Promise |
TYPE | char20_arr | IS | TABLE | of | varchar2(20Available-To-Promise |
TYPE | char30_arr | IS | TABLE | of | varchar2(30Available-To-Promise |
TYPE | char40_arr | IS | TABLE | of | varchar2(40Available-To-Promise |
TYPE | char80_arr | IS | TABLE | of | varchar2(80Available-To-Promise |
TYPE | char2000_arr | IS | TABLE | of | varchar2(2000); |
TYPE | date_arr | IS | TABLE | of | date; |
Call MSC_ATP_CLOBAL.Extend_ATP for extending this record
TYPE ATP_Rec_Typ is RECORD
Row_Id | char30_arr, |
Instance_Id | number_arr, |
Inventory_Item_Id | number_arr, |
Inventory_Item_Name | char40_arr, |
Source_Organization_Id | number_arr, |
Source_Organization_Code | char7_arr, |
Organization_Id | number_arr, |
Identifier | number_arr, |
Demand_Source_Header_Id | number_arr, |
Demand_Source_Delivery | char30_arr, |
Demand_Source_Type | number_arr, |
Scenario_Id | number_arr, |
Calling_Module | number_arr, |
Customer_Id | number_arr, |
Customer_Site_Id | number_arr, |
Destination_Time_Zone | char30_arr, |
Quantity_Ordered | number_arr, |
Quantity_UOM | char3_arr, |
Requested_Ship_Date | date_arr, |
Requested_Arrival_Date | date_arr, |
Earliest_Acceptable_Date | date_arr, |
Latest_Acceptable_Date | date_arr, |
Delivery_Lead_Time | number_arr, |
Freight_Carrier | char30_arr, |
Ship_Method | char30_arr, |
Demand_Class | char30_arr, |
Ship_Set_Name | char30_arr, |
Arrival_Set_Name | char30_arr, |
Override_Flag | char1_arr, |
Action | number_arr, |
Ship_Date | date_arr, |
Arrival_Date | date_arr, |
Available_Quantity | number_arr, |
Requested_Date_Quantity | number_arr, |
Group_Ship_Date | date_arr, |
Group_Arrival_Date | date_arr, |
Vendor_Id | number_arr, |
Vendor_Name | char80_arr, |
Vendor_Site_Id | number_arr, |
Vendor_Site_Name | char80_arr, |
Insert_Flag | number_arr, |
OE_Flag | char1_arr, |
Atp_Lead_Time | number_arr, |
Error_Code | number_arr, |
Message | char2000_arr, |
End_Pegging_Id | number_arr, |
Order_Number | number_arr, |
Old_Source_Organization_Id | number_arr, |
Old_Demand_Class | char30_arr |
Ato_delete_flag | char1_arr, |
Attribute_01 | number_arr, |
Attribute_02 | number_arr, |
Attribute_03 | number_arr, |
Attribute_04 | number_arr, |
Attribute_05 | char30_arr, |
Attribute_06 | char30_arr, |
Attribute_07 | char30_arr, |
Attribute_08 | char30_arr, |
Attribute_09 | date_arr, |
Attribute_10 | date_arr, |
Customer_name | char80_arr, |
Customer_class | char30_arr, |
Customer_location | char40_arr, |
Customer_country | char60_arr, |
Customer_state | char60_arr, |
Customer_city | char60_arr, |
Customer_postal_code | char60_arr, |
Substitution_typ_code | number_arr, |
Req_item_detail_flag | number_arr, |
Request_item_id | number_arr, |
Req_item_req_date_qty | number_arr, |
Req_item_available_date | date_arr, |
Req_item_available_date_qty | number_arr, |
Request_item_name | char40_arr, |
Old_inventory_item_id | number_arr, |
Sales_rep | char255_arr, |
Customer_contact | char255_arr, |
Subst_flag | number_arr, |
Top_Model_line_id | number_arr, |
ATO_Parent_Model_Line_Id | number_arr, |
ATO_Model_Line_Id | number_arr, |
Parent_line_id | number_arr, |
Match_item_id | number_arr, |
Config_item_line_id | number_arr, |
Validation_Org | number_arr, |
Component_Sequence_ID | number_arr, |
Component_Code | char255_arr, |
Line_number | char80_arr, |
Included_item_flag | number_arr, |
Atp_flag | char1_arr, |
Atp_components_flag | char1_arr, |
Wip_supply_type | number_arr, |
Bom_item_type | number_arr, |
Mandatory_item_flag | number_arr, |
Pick_components_flag | char1_arr, |
Base_model_id | number_arr, |
Oss_error_code | number_arr, |
Matched_item_name | char255_arr, |
Cascade_model_info_to_comp | number_arr, |
Sequence_number | number_arr, |
Firm_flag | number_arr, |
Order_line_number | number_arr, |
Option_number | number_arr, |
Shipment_number | number_arr, |
Item_desc | char255_arr, |
Old_line_schedule_date | date_arr, |
Old_source_organization_code | char7_arr, |
Firm_source_org_id | number_arr, |
Firm_source_org_code | char7_arr, |
Firm_ship_date | date_arr, |
Firm_arrival_date | date_arr, |
Ship_method_text | char255_arr, |
Ship_set_id | number_arr, |
Arrival_set_id | number_arr, |
Project_id | number_arr, |
Task_id | number_arr, |
Project_number | char30_arr, |
Task_Number | char30_arr, |
Attribute_11 | number_arr, |
Attribute_12 | number_arr, |
Attribute_13 | number_arr, |
Attribute_14 | number_arr, |
Attribute_15 | char30_arr, |
Attribute_16 | char30_arr, |
Attribute_17 | char30_arr, |
Attribute_18 | char30_arr, |
Attribute_19 | date_arr, |
Attribute_20 | date_arr, |
Attribute_21 | number_arr, |
Attribute_22 | number_arr, |
Attribute_23 | number_arr, |
Attribute_24 | number_arr, |
Attribute_25 | char30_arr, |
Attribute_26 | char30_arr, |
Attribute_27 | char30_arr, |
Attribute_28 | char30_arr, |
Attribute_29 | date_arr, |
Attribute_30 | date_arr, |
Atf_date | date_arr, |
Plan_id | number_arr, |
Original_request_date | date_arr, |
Receiving_cal_code | char14_arr, |
Intransit_cal_code | char14_arr, |
Shipping_cal_code | char14_arr, |
Manufacturing_cal_code | char14_arr, |
Internal_org_id | number_arr, |
First_valid_ship_arrival_date | date_arr |
Party_site_id | number_arr, |
1. | Row_Id: The row_id in database for an order. This field is used only in 10.7 and 11.0 versions of application. This field is optional for later versions. |
2. | Instance_Id: Instance identifiers of the requesting module. This is mandatory if calling_module is 724. For other calling modules, instance_id is obtained from MRP_AP_APPS_INSTANCES. |
3. | Inventory_Item_Id: Inventory Item ID for which the ATP check needs to be done. This field is mandatory. |
4. | Inventory_Item_Name: Name of the items. If not provided, then ATP may populate this field. |
5. | Source_Organization_Id: Shipping Organization ID. This is the inventory organization that you want the ATP check performed against. If not provided, ATP calculates the shipping organization ID using sourcing rules based on provided customer_site_id/organization_id. |
6. | Source_Organization_Code: Shipping Organization Code. ATP populates this field based on Source_Organization_Id. |
7. | Organization_Id: Receiving organization ID. Either organization_id or customer_id must be provided but both should not be provided. |
8. | Identifier: Order line ID. This field is mandatory for scheduling, unscheduling, and rescheduling. |
9. | Demand_Source_Header_Id: Header ID for Order. This field is not mandatory. |
10. | Demand_Source_Delivery: This field is used along with demand_source_header_id and demand_source_type to uniquely identify an order in Order Management. This field is not mandatory. |
11. | Demand_Source_Type: This field is used along with demand_source_header_id and demand_source_delivery to uniquely identify an order in Order Management. This field is not mandatory. |
12. | Scenario_Id: This field is for ATP internal use. |
13. | Calling_Module: Module that called ATP.
|
14. | Customer_Id: ID of the customer for whom ATP check needs to be done. Either organization_id or customer_id must be provided but both should not be provided. |
15. | Customer_Site_Id: Ship to Site ID of the receiving Customer Site. If this field is not provided then ATP cannot do global sourcing and ship method/delivery lead time calculation. |
16. | Destination_Time_Zone: Time zone of the requesting organization. ATP does not support this field at present. |
17. | Quantity_Ordered: Quantity ordered for the items expressed in Quantity_UOM. This field is mandatory. For unscheduling, this field must be 0. |
18. | Quantity_UOM: Unit of measurement of items ordered. This field is mandatory. |
19. | Requested_Ship_Date: Requested ship date for the items. Either requested_ship_date or requested_arrival_date must be provided but both should not be provided. |
20. | Requested_Arrival_Date: Requested arrival date for the items. Either requested_ship_date or requested_arrival_date must be provided but both should not be provided. |
21. | Earliest_Acceptable_Date: Earliest acceptable date by which the requester is ready to accept the order in case ATP check fails on requested ship or arrival date. This feature is not used by ATP at present. |
22. | Latest_Acceptable_Date: Latest acceptable date by which the requester is ready to accept the order in case ATP check fails on requested ship or arrival date. |
23. | Delivery_Lead_Time: Delivery lead time between shipping and receiving organization. If not provided, then ATP calculates it based on ship method provided to ATP or else default ship method setup between ship-from Org and ship-to site. Customer_Site_ID must be provided for ATP to make this calculation. |
24. | Freight_Carrier: Freight Carrier used for the shipment. This feature is not used by ATP at present. |
25. | Ship_Method: Ship method to be used for shipping. If delivery_lead_time is provided then this is not required. Otherwise, ATP tries to calculate delivery_lead_time based on provided ship method. If the ship_method provided is not a valid one between the source organization and receiving organization/customer, then ATP uses the default shipping method. If the default shipping method is set between the source organization and receiving organization/customer, then ATP will assign the default ship method to this field else this field will be left empty. Customer_Site_ID must be provided for ATP to make this calculation. |
26. | Demand_Class: Demand class under which customer or requesting organization falls. This field is not mandatory. |
27. | Ship_Set_Name: Name of the ship-set. For line items, this field remains empty. Either Ship_set_name or Arrival_Set_Name should be passed, and not both. All lines in a set must be passed consecutively. |
28. | Arrival_Set_Name: Name of the arrival-set. For line items, this field remains empty. Either Ship_set_name or Arrival_Set_Name should be passed, and not both. |
29. | Override_Flag: Indicates ATP to honor the requested date irrespective of availability of the requested items. Possible values:
|
30. | Action: Type of Inquiry. This field is mandatory. Possible Values:
|
31. | Ship_Date: Date on which requested item will be shipped. This field is populated by ATP. |
32. | Arrival_Date: Date on which requested item will arrive. This field is populated by ATP. |
33. | Available_Quantity: Quantity available on ship date. This field is populated by ATP. |
34. | Requested_Date_Quantity: Quantity available on requested ship/arrival date. This field is populated by ATP. |
35. | Group_Ship_Date: Ship date for whole ship set. This field is populated by ATP in case of ship set. |
36. | Group_Arrival_Date: Arrival date for arrival set. This field is populated by ATP for both ship set and arrival set. |
37. | Vendor_Id: Vendor ID from where item needs to be requested. This field is not used by ATP. |
38. | Vendor_Name: Vendor Name. This field is not used by ATP. |
39. | Vendor_Site_Id: ID of vendor site from where item needs to be requested. This field is not used by ATP. |
40. | Vendor_Site_Name: Vendor site name. This field is not used by ATP. |
41. | Insert_Flag: Flag to indicate if supply/demand and period details are calculated or not. If this field is set to 1, then ATP calculates supply/demand and period details. Unless the user needs to see supply demand details, for performance reasons this field should be set to something other than 1. |
42. | OE_Flag: Indicates if it is an internal sales order or not. Possible values:
|
43. | Atp_Lead_Time: ATP Lead Time for Configure-to-Order Models/ Option Classes/ Option Items etc. This field is populated by ATP. |
44. | Error_Code: Error code of the error occurred during ATP check. Check MTL_DEMAND_INTERFACE _ERRORS lookup for a complete list of error codes and corresponding error messages. |
45. | Message: Error message for the error occurred during ATP check. This field is not used by ATP. |
46. | End_Pegging_Id: Pegging ID for the ultimate parent. This field is populated by ATP. |
47. | Order_Number: Order number in Order management. |
48. | Old_Source_Organization_Id: This field is used for unscheduling/rescheduling and indicates ID of Organization where item was scheduled initially. |
49. | Old_Demand_Class: Used for unscheduling/rescheduling and indicates the demand class under which item was scheduled initially. |
50. | Ato_delete_flag: Indicates if the item requested for Unscheduling is part of an ATO Model. Possible values are Y or N. This field is obsolete in 11.5.10. |
51. | Attribute_01: Used for passing source document line id for internal sales orders. |
52. | Attribute_02: Used for diagnostic ATP.
|
53. | Attribute_03: Reserved for future ATP functionalities. |
54. | Attribute_04: ATP uses this flag internally to pass refresh number in 24x7 processing. |
55. | Attribute_05: ATP uses this flag internally to pass visible demand flag for ATO items. |
56. | Attribute_06: ATP uses this flag internally to pass ATP_FLAG for an item from source to destination |
57. | Attribute_07: ATP uses this flag internally to pass back the name of the plan used by ATP for inquiry. |
58. | Attribute_08: Reserved for future ATP functionalities. |
59. | Attribute_09: Reserved for future ATP functionalities. |
60. | Attribute_10: Reserved for future ATP functionalities. |
61. | Customer_name: Name of ship-to customer entered on the sales order pad. Currently, this field is not used by ATP. |
62. | Customer_class: Reserved for future ATP functionalities. |
63. | Customer_location: Customer location of ship-to customer entered on the sales order pad. Currently, this field is not used by ATP. |
64. | Customer_country: Country of ship-to customer entered on the sales order pad. |
65. | Customer_state: State of ship-to customer entered on the sales order pad. |
66. | Customer_city: City of ship-to customer entered on the sales order pad. |
67. | Customer_postal_code: Postal code of ship-to customer entered on the sales order pad. |
68. | Substitution_typ_code: Type of substitution that should be performed on the line. Possible values:
|
69. | Req_item_detail_flag: Indicates whether ATP details of original items should be provided or not in case a substitute is used to satisfy the demand.
|
70. | Request_item_id: Source inventory item id of the requested item in case substitute is used to satisfy the demand. |
71. | Req_item_req_date_qty: Request date quantity for requested item. This field is populated by ATP only if the Req_item_detail_flag field is set to 1 and susbtitution occurs. . |
72. | Req_item_available_date: Date on which requested item is available. This field is populated by ATP only if the Req_item_detail_flag field is set to 1 and substitution occurs. |
73. | Req_item_available_date_qty: Quantity of requested item on ATP date. This field is populated by ATP only if the Req_item_detail_flag field is set to 1. This field is populated only if substitution occurs. |
74. | Request_item_name: Name of the requested item. This field is populated only if substitution occurs. |
75. | Old_inventory_item_id: Source inventory item ID for the item used during last scheduling session for the line. |
76. | Sales_rep: Name of the sales representatives listed on the order line. If this is not provided, then workflow notification is not sent in case of substitution. |
77. | Customer_contact: Name of the customer contact listed on the order line. If this is not provided, then workflow notification is not sent in case of substitution. |
78. | Subst_flag: Contains 1 if substitution occurs for the line. |
79. | Top_Model_line_id: Line ID of the top model for an ATO/PTO configuration |
80. | ATO_Parent_Model_Line_Id: Line ID of parent ATO configuration. |
81. | ATO_Model_Line_Id: Line ID of the top ATO model configuration. |
82. | Parent_line_id: Line ID of the parent item in case of ATO/PTO models. |
83. | Match_item_id: Source inventory item ID for the matched configuration. |
84. | Config_item_line_id: Line ID of the configuration item linked to a sales order. |
85. | Validation_Org: Validation organization ID for the calling instance. |
86. | Component_Sequence_ID: Sequence ID of an option item/class in the BOM of an ATO model. |
87. | Component_Code: Component code of an option item/class in the BOM of an ATO model. |
88. | Line_number: Line number of an item on sales order. |
89. | Included_item_flag: Indicates whether calling module has already exploded included items for a PTO model/Kit or not.
|
90. | Atp_flag: ATP flag for an item. This field is for internal ATP use. . |
91. | Atp_components_flag: ATP Components flag for an item. This field is for internal ATP use. |
92. | Wip_supply_type: WIP Supply type for an item. This field is for internal ATP use. |
93. | Bom_item_type: BOM item type for an item. This field is for internal ATP use. |
94. | Mandatory_item_flag: Indicates whether the item is mandatory for PTO model or not. This field is applicable only when the Included_item_flag field is set to 2. This field is for internal ATP use. |
95. | Pick_components_flag: Pick components flag for an item. |
96. | Base_model_id: Inventory item id for the base model for a matched configuration. |
97. | Oss_error_code: Code of the error encountered while evaluating option specific sourcing. |
98. | Matched_item_name: Name of the matched configuration. This field is populated by ATP in case matched ATO configuration is found. |
99. | Cascade_model_info_to_comp: Indicates whether availability result information for top ATO model should be cascaded to its components or not. Possible values:
|
100. | Sequence_number: Sequence in which items are passed to ATP for availability check. |
101. | Firm_flag: Indicates whether line has been firmed or not. This field is specifically used for Order Backlog Workbench. |
102 | Order_line_number: Line number for an item on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
103. | Option_number: Number for on option on Order backlog workbench. This field is specifically used for order backlog workbench. |
104. | Shipment_number: Shipment number for on option on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
105. | Item_desc: Description of an item on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
106. | Old_line_schedule_date: Old schedule date for a give line on Order Backlog Workbench. This field is specifically used for Order Backlog Workbench. |
107. | Old_source_organization_code: Code of an organization in which order was last scheduled. This field is specifically used for Order Backlog Workbench. |
108. | Firm_source_org_id: Code of an organization in which order was last scheduled. This field is specifically used for Order Backlog Workbench. |
109. | Firm_source_org_code: Code of the source organization. This field is specifically used for Order Backlog Workbench. |
110. | Firm_ship_date: Firm ship date. This field is specifically used for Order Backlog Workbench. |
111. | Firm_arrival_date: Firm arrival date. This field is specifically used for Order Backlog Workbench. |
112. | Ship_method_text: Ship method description. This field is specifically used for Order Backlog Workbench. |
113. | Ship_set_id: ID for the ship set. This field is specifically used for Order Backlog Workbench. |
114. | Arrival_set_id: ID for arrival set. This field is specifically used for Order Backlog Workbench. |
115. | Project_ID: ID of the project with which line is associated. This field is specifically used for Order Backlog Workbench. |
116. | Task_ID: ID of the task with which line is associated. This field is specifically used for Order Backlog Workbench. |
117. | Project_number: Project number. This field is specifically used for Order Backlog Workbench. |
118. | Task_number: Task number. This field is specifically used for Order Backlog Workbench. |
119. | Attribute_11: Reserved for future ATP functionalities. |
120. | Attribute_12: Reserved for future ATP functionalities. |
121. | Attribute_13: Reserved for future ATP functionalities. |
122. | Attribute_14: Reserved for future ATP functionalities. |
123. | Attribute_15: Reserved for future ATP functionalities. |
124. | Attribute_16: Reserved for future ATP functionalities. |
125. | Attribute_17: Reserved for future ATP functionalities |
126. | Attribute_18: Reserved for future ATP functionalities. |
127. | 127Attribute_19: Reserved for future ATP functionalities. |
128. | Attribute_20: Reserved for future ATP functionalities. |
129. | Attribute_21: Reserved for future ATP functionalites. |
130. | Attribute_22: Reserved for future ATP functionalities. |
131. | Attribute_23: Reserved for future ATP functionalities. |
132. | Attribute_24: Reserved for future ATP functionalities. |
133. | Attribute_25: Reserved for future ATP functionalities. |
134. | Attribute_26: Reserved for future ATP functionalities. |
135. | Attribute_27: Reserved for future ATP functionalities. |
136. | Attribute_28: Reserved for future ATP functionalities. |
137. | Attribute_29: Reserved for future ATP functionalities. |
138. | Attribute_30: Reserved for future ATP functionalities. |
139. | Atf_date: ATF date associated with the combined item-product family item. This field is used for internal ATP processing. |
140. | Plan_id: ID of the plan used to satisfy the demand. |
141. | Original_request_date: Original request date for the order. This field is used for internal ATP processing. |
142. | Receiving_cal_code: Code for the receiving calendar of the customer associated with the line. This field is used for internal ATP processing. |
143. | Intransit_cal_code: Code for the In-transit calendar for the customer associated with the line and the source organization. This field is used for internal ATP processing. |
144. | Shipping_cal_code: Code for the shipping calendar of the source organization. This field is used for internal ATP processing. |
145. | Manufacturing_cal_code: Code for the manufacturing calendar of the manufacturing organization. This field is used for internal ATP processing. |
146. | Internal_org_id: ID of the receiving organization in case of internal sales order. |
147. | First_valid_ship_arrival_date: If the request date type is Ship, this field contains the first valid ship date after the system date as per the shipping calendar for the source organization. If the request date type is Arrival, then this field contains the first valid arrival date after the system date as per the receiving calendar of the customer. |
148. | Party_site_ID: This field contains party site indentifier for ship-to customer site |
149. | Part_of_set: Used in the context of lines that are added to an existing set. If it is set to Y, ATP will validate the scheduled date with the date passed by Oracle Order management for the existing set. If the scheduled date does not meet the date, it will fail. If it fails, ATP removes the pegging created since leaving it might lead to dual consumption. |
Either requested_ship_date or requested_arrival_date should be provided. Error will be generated if none or both of these dates are provided
If delivery lead time and source organization id are specified then organization_id and customer_site_id could be null. If either delivery lead time or source organization are not specified, then at least one of these fields should be populated to enable ATP to do global sourcing and delivery lead time calculation.
Instance_ID must be provided if calling_module is 724.
Inventory_Item_ID field should contain a valid inventory item ID.
Quantity_ordered field should contain a valid quantity.
Quantity_UOM should contain a valid unit of measurement value.
Action field should contain a valid Action type. See the description of action field for valid values.
Old_Source_Organization_id and Old_Demand_class should be provided in case of order rescheduling.
Substitution_typ_code should always be populated if substitution needs to be done for the item.
Old_inventory_item_id should always be populated for a substituted line in case of order rescheduling.
Top_Model_line_id, ATO_Model_Line_Id, Parent_line_id, Config_item_line_id, Component_Sequence_ID and Component_Code fields should always be populated for Inquiry on ATO models.
Either Validation_Org or Source_organization_id field should always be populated.
TYPE ATP_Supply_Demand_Typ is RECORD
Col. 1 | Col. 2 |
---|---|
Level | number_arr, |
Identifier | number_arr, |
Inventory_Item_Id | number_arr, |
Request_Item_Id | number_arr, |
Organization_Id | number_arr, |
Department_Id | number_arr, |
Resource_Id | number_arr, |
Supplier_Id | number_arr, |
Supplier_Site_Id | number_arr, |
From_Organization_Id | number_arr, |
From_Location_Id | number_arr, |
To_Organization_Id | number_arr, |
To_Location_Id | number_arr, |
Ship_Method | char30_arr, |
Uom | char3_arr, |
Disposition_Type | number_arr, |
Disposition_Name | char80_arr, |
Identifier1 | number_arr, |
Identifier2 | number_arr, |
Identifier3 | number_arr, |
Identifier4 | number_arr, |
Supply_Demand_Type | number_arr, |
Supply_Demand_Source_Type | number_arr, |
Supply_Demand_Source_Type_Name | char80_arr, |
Supply_Demand_Date | date_arr, |
Supply_Demand_Quantity | number_arr, |
Scenario_Id | number_arr, |
Pegging_Id | number_arr, |
End_Pegging_Id | number_arr, |
Original_Item_Id | number_arr, |
Original_Supply_Demand_Type | number_arr, |
Original_Demand_Date | date_arr, |
Original_Demand_Quantity | number_arr, |
Allocated_Quantity | number_arr, |
Pf_Display_Flag | number_arr, |
Level: Indicates the level of supply/demand in pegging.
Identifier: A unique identifier to identify a line (Order line number in case of OM).
Inventory_Item_Id: Inventory item ID (Product Family ID in case of product family).
Request_Item_Id: Inventory Item ID.
Organization_Id: Organization ID of Organization where supply/demand is placed.
Department_Id: Department ID of the department to which resource belongs.
Resource_Id: Resource ID.
Supplier_Id: Supplier ID.
Supplier_Site_Id: Supplying Site ID.
From_Organization_Id: Shipping Organization ID. This field is not used by ATP at present.
From_Location_Id: Shipping Location ID. This field is not used by ATP at present.
To_Organization_Id: Receiving Organization ID. This field is not used by ATP at present.
To_Location_Id: Receiving Location ID. This field is not used by ATP at present.
Ship_Method: Ship Method Used. This field is not used by ATP at present.
Uom: Unit of Measurement.
Disposition_Type: This field is not used by ATP.
Disposition_Name: This field contains Order Number.
Identifier1: This field contains instance ID.
Identifier2: This field is not used by ATP.
Identifier3: This field contains demand ID in case of demand, and transaction ID in case of supplies for resource or components.
Identifier4: This field is not used by ATP.
Supply_Demand_Type: Type of supply demand. Possible values:
1 - Demand
2 - Supply
Supply_Demand_Source_Type: Type of Supply/Demand.
Supply_Demand_Source_Type_Name: This field is not used by ATP at present.
Supply_Demand_Date: Date of Supply/Demand.
Supply_Demand_Quantity: Supply/Demand Quantity.
Scenario_Id: This field is not used by ATP at present.
Pegging_Id: Pegging ID for the current record.
End_Pegging_Id: Top Parent's pegging ID.
Original_Item_Id: ID of the Original Item
Original_Supply_Demand_Type: Type of the original supply/demand. This is applicable only for supplies and demands of items that are members of time-phased enabled product families.
Original_Demand_Date: Date of the original demand. This is applicable only for demands of items that are members of time-phased enabled product families.
Original_Demand_Quantity: Quantity of the original demand. This is applicable only for demands of items that are members of time-phased enabled product families.
Allocated_Quantity: Allocated quantity of the supply/demand - This field is used for internal ATP processing.
Pf_Display_Flag: Indicates whether to display in ATP supply demand window.
TYPE ATP_Period_Typ is Record
Col. 1 | Col. 2 |
---|---|
Level | number_arr, |
Identifier | number_arr, |
Inventory_Item_Id | number_arr, |
Request_Item_Id | number_arr, |
Organization_Id | number_arr, |
Department_Id | number_arr, |
Resource_Id | number_arr, |
Supplier_Id | number_arr, |
Supplier_Site_Id | number_arr, |
From_Organization_Id | number_arr, |
From_Location_Id | number_arr, |
To_Organization_Id | number_arr, |
To_Location_Id | number_arr, |
Ship_Method | char30_arr, |
UOM | char3_arr, |
Total_Supply_Quantity | number_arr, |
Total_Demand_Quantity | number_arr, |
Period_Start_Date | date_arr, |
Period_End_Date | date_arr, |
Period_Quantity | number_arr, |
Cumulative_Quantity | number_arr, |
Identifier1 | number_arr, |
Identifier2 | number_arr, |
Scenario_Id | number_arr, |
Pegging_Id | number_arr, |
End_Pegging_Id | number_arr, |
Identifier4 | number_arr, |
Demand_Class | char80_arr, |
Class | char80_arr, |
Customer_Id | number_arr, |
Customer_Site_Id | number_arr, |
Allocated_Supply_Quantity | number_arr, |
Supply_Adjustment_Quantity | number_arr, |
Backward_Forward_Quantity | number_arr, |
Backward_Quantity | number_arr, |
Demand_Adjustment_Quantity | number_arr, |
Adjusted_Availability_Quantity | number_arr, |
Adjusted_Cum_Quantity | number_arr, |
Unallocated_Supply_Quantity | number_arr, |
Unallocated_Demand_Quantity | number_arr, |
Unallocated_Net_Quantity | number_arr, |
Total_Bucketed_Demand_Quantity | number_arr, |
Unalloc_Bucketed_Demand_Qty | number_arr |
Level: Indicates the level of supply/demand in pegging.
Identifier: A unique identifier to identify a line (Order line ID in case of OM).
Inventory_Item_Id: Inventory Item ID (Product family ID in case of product family).
Request_Item_Id: Inventory Item ID.
Organization_Id: Organization ID of the organization where supply/demand is placed.
Department_Id: Department ID of the department to which resource belongs.
Resource_Id: Resource ID.
Supplier_Id: Supplier ID.
Supplier_Site_Id: Supplying site ID.
From_Organization_Id: Shipping Organization ID. This field is not used by ATP at present.
From_Location_Id: Shipping Location ID. This field is not used by ATP at present.
To_Organization_Id: Receiving Organization ID. This field is not used by ATP at present.
To_Location_Id: Shipping Organization ID. This field is not used by ATP at present.
Ship_Method: Ship Method used. This field is not used by ATP at present.
Uom: Unit of Measurement.
Total_Supply_Quantity: Total supplies for a period.
Total_Demand_Quantity: Total demands for a period.
Period_Start_Date: Start date for a period.
Period_End_Date: End date for a period.
Period_Quantity: Net Supply-Demand quantity for that period.
Cumulative_Quantity: Cumulative quantity for a period after doing backward consumption, forward consumption and accumulation.
Identifier1: Instance ID.
Identifier2: This field is not used by ATP.
Scenario_Id: This field is for ATP internal use.
Pegging_Id: Pegging ID for the current record.
End_Pegging_Id: Pegging ID of the top parent.
Identifier4: Sysdate allocation percentage. Used by allocation workbench during allocated ATP based on user defined allocation percentage.
Demand_Class: Demand class. Used by allocation workbench.
Class: Customer class. Used by allocation workbench.
Customer_Id: Customer ID. Used by allocation workbench.
Customer_Site_Id: Customer site ID. Used by allocation workbench.
Allocated_Supply_Quantity: Supply allocated to a demand class on a date. Used by allocation workbench.
Supply_Adjustment_Quantity: Supply adjustment. Used by allocation workbench.
Backward_Forward_Quantity: Figures after backward and forward consumption. Used by allocation workbench.
Backward_Quantity: Figures after backward consumption. Used by allocation workbench.
Demand_Adjustment_Quantity: Demand adjustment. Used by allocation workbench.
Adjusted_Availability_Quantity: Figures after demand class consumption. Used by allocation workbench.
Adjusted_Cum_Quantity: Adjusted cumulative quantity. Used by allocation workbench.
Unallocated_Supply_Quantity: Unallocated supply. Used by allocation workbench.
Unallocated_Demand_Quantity: Unallocated demand. Used by allocation workbench.
Unallocated_Net_Quantity: Unallocated net. Used by allocation workbench.
Total_Bucketed_Demand_Quantity: Bucketed Demand. Used only in PF time phased ATP.
Unalloc_Bucketed_Demand: Unallocated bucketed demand. Used in rule based and time phased ATP.
TYPE ATP_Details_Typ is RECORD
Col. 1 | Col. 2 |
---|---|
Level | number_arr, |
Identifier | number_arr, |
Request_Item_Id | number_arr, |
Request_Item_Name | char40_arr, |
Inventory_Item_Id | number_arr, |
Inventory_Item_Name | char40_arr, |
Organization_Id | number_arr, |
Organization_Code | char3_arr, |
Department_Id | number_arr, |
Department_Code | char10_arr, |
Resource_Id | number_arr, |
Resource_Code | char10_arr, |
Supplier_Id | number_arr, |
Supplier_Name | char80_arr, |
Supplier_Site_Id | number_arr, |
From_Organization_Id | number_arr, |
From_Organization_Code | char3_arr, |
From_Location_Id | number_arr, |
From_Location_Code | char20_arr, |
To_Organization_Id | number_arr, |
To_Organization_Code | char3_arr, |
To_Location_Id | number_arr, |
To_Location_Code | char20_arr, |
Ship_Method | char30_arr, |
Uom | char3_arr, |
Supply_Demand_Type | number_arr, |
Supply_Demand_Quantity | number_arr, |
Source_Type | number_arr, |
Identifier1 | number_arr, |
Identifier2 | number_arr, |
Identifier3 | number_arr, |
Identifier4 | number_arr, |
Scenario_Id | number_arr |
Available-To-Promise
ATP does not use ATP_Details_Typ at present.
Type MSC_ATP_CUSTOM is package.
This package provides the framework for customers and consultants to:
Extend the ATP post plan allocation
Manipulate the output of ATP Call
Extend the ATP post plan allocation
Before ATP post plan allocation, a call is made to the hook MSC_ATP_CUSTOM.Custom_Pre_Allocation, passing the plan_id as a parameter. In the hook, custom code can be written for any processing before ATP post plan allocation.
Note: All the exceptions raised are caught in the calling procedure and ATP post plan allocation continues as if there were no exception.
Manipulate the output of ATP Call
After ATP call is made, then a call is made to the hook MSC_ATP_CUSTOM. Custom_Post_ATP_API with parameter details.
p_atp_rec -- Input table. This table contains information generated by ATP engine. This is same as MRP_ATP_PUB.ATP_Rec_Typ for which details are given in CALL_ATP API public documentation.
x_atp_rec -- Output table. This table contains modified information.
x_modify_flag -- This flag indicates whether information generated by ATP is modified in this API or not. Values:
1- Information has been modified
2- No Changes
x_return_status -- Return Status from the API
To print any debug message in the concurrent program log file a call could be made to the procedure MSC_UTIL.Msc_Log passing the string to be printed as a parameter.
Call MSC_ATP_CLOBAL.Extend_ATP for extending this record
TYPE ATP_Rec_Typ is RECORD
Row_Id | char30_arr, |
Instance_Id | number_arr, |
Inventory_Item_Id | number_arr, |
Inventory_Item_Name | char40_arr, |
Source_Organization_Id | number_arr, |
Source_Organization_Code | char7_arr, |
Organization_Id | number_arr, |
Identifier | number_arr, |
Demand_Source_Header_Id | number_arr, |
Demand_Source_Delivery | char30_arr, |
Demand_Source_Type | number_arr, |
Scenario_Id | number_arr, |
Calling_Module | number_arr, |
Customer_Id | number_arr, |
Customer_Site_Id | number_arr, |
Destination_Time_Zone | char30_arr, |
Quantity_Ordered | number_arr, |
Quantity_UOM | char3_arr, |
Requested_Ship_Date | date_arr, |
Requested_Arrival_Date | date_arr, |
Earliest_Acceptable_Date | date_arr, |
Latest_Acceptable_Date | date_arr, |
Delivery_Lead_Time | number_arr, |
Freight_Carrier | char30_arr, |
Ship_Method | char30_arr, |
Demand_Class | char30_arr, |
Ship_Set_Name | char30_arr, |
Arrival_Set_Name | char30_arr, |
Override_Flag | char1_arr, |
Action | number_arr, |
Ship_Date | date_arr, |
Arrival_Date | date_arr, |
Available_Quantity | number_arr, |
Requested_Date_Quantity | number_arr, |
Group_Ship_Date | date_arr, |
Group_Arrival_Date | date_arr, |
Vendor_Id | number_arr, |
Vendor_Name | char80_arr, |
Vendor_Site_Id | number_arr, |
Vendor_Site_Name | char80_arr, |
Insert_Flag | number_arr, |
OE_Flag | char1_arr, |
Atp_Lead_Time | number_arr, |
Error_Code | number_arr, |
Message | char2000_arr, |
End_Pegging_Id | number_arr, |
Order_Number | number_arr, |
Old_Source_Organization_Id | number_arr, |
Old_Demand_Class | char30_arr |
Ato_delete_flag | char1_arr, |
Attribute_01 | number_arr, |
Attribute_02 | number_arr, |
Attribute_03 | number_arr, |
Attribute_04 | number_arr, |
Attribute_05 | char30_arr, |
Attribute_06 | char30_arr, |
Attribute_07 | char30_arr, |
Attribute_08 | char30_arr, |
Attribute_09 | date_arr, |
Attribute_10 | date_arr, |
Customer_name | char80_arr, |
Customer_class | char30_arr, |
Customer_location | char40_arr, |
Customer_country | char60_arr, |
Customer_state | char60_arr, |
Customer_city | char60_arr, |
Customer_postal_code | char60_arr, |
Substitution_typ_code | number_arr, |
Req_item_detail_flag | number_arr, |
Request_item_id | number_arr, |
Req_item_req_date_qty | number_arr, |
Req_item_available_date | date_arr, |
Req_item_available_date_qty | number_arr, |
Request_item_name | char40_arr, |
Old_inventory_item_id | number_arr, |
Sales_rep | char255_arr, |
Customer_contact | char255_arr, |
Subst_flag | number_arr, |
Top_Model_line_id | number_arr, |
ATO_Parent_Model_Line_Id | number_arr, |
ATO_Model_Line_Id | number_arr, |
Parent_line_id | number_arr, |
Match_item_id | number_arr, |
Config_item_line_id | number_arr, |
Validation_Org | number_arr, |
Component_Sequence_ID | number_arr, |
Component_Code | char255_arr, |
Line_number | char80_arr, |
Included_item_flag | number_arr, |
Atp_flag | char1_arr, |
Atp_components_flag | char1_arr, |
Wip_supply_type | number_arr, |
Bom_item_type | number_arr, |
Mandatory_item_flag | number_arr, |
Pick_components_flag | char1_arr, |
Base_model_id | number_arr, |
Oss_error_code | number_arr, |
Matched_item_name | char255_arr, |
Cascade_model_info_to_comp | number_arr, |
Sequence_number | number_arr, |
Firm_flag | number_arr, |
Order_line_number | number_arr, |
Option_number | number_arr, |
Shipment_number | number_arr, |
Item_desc | char255_arr, |
Old_line_schedule_date | date_arr, |
Old_source_organization_code | char7_arr, |
Firm_source_org_id | number_arr, |
Firm_source_org_code | char7_arr, |
Firm_ship_date | date_arr, |
Firm_arrival_date | date_arr, |
Ship_method_text | char255_arr, |
Ship_set_id | number_arr, |
Arrival_set_id | number_arr, |
Project_id | number_arr, |
Task_id | number_arr, |
Project_number | char30_arr, |
Task_Number | char30_arr, |
Attribute_11 | number_arr, |
Attribute_12 | number_arr, |
Attribute_13 | number_arr, |
Attribute_14 | number_arr, |
Attribute_15 | char30_arr, |
Attribute_16 | char30_arr, |
Attribute_17 | char30_arr, |
Attribute_18 | char30_arr, |
Attribute_19 | date_arr, |
Attribute_20 | date_arr, |
Attribute_21 | number_arr, |
Attribute_22 | number_arr, |
Attribute_23 | number_arr, |
Attribute_24 | number_arr, |
Attribute_25 | char30_arr, |
Attribute_26 | char30_arr, |
Attribute_27 | char30_arr, |
Attribute_28 | char30_arr, |
Attribute_29 | date_arr, |
Attribute_30 | date_arr, |
Atf_date | date_arr, |
Plan_id | number_arr, |
Original_request_date | date_arr, |
Receiving_cal_code | char14_arr, |
Intransit_cal_code | char14_arr, |
Shipping_cal_code | char14_arr, |
Manufacturing_cal_code | char14_arr, |
Internal_org_id | number_arr, |
First_valid_ship_arrival_date | date_arr |
Party_site_id | number_arr, |
1. | Row_Id: The row_id in database for an order. This field is used only in 10.7 and 11.0 versions of application. This field is optional for later versions. |
2. | Instance_Id: Instance identifiers of the requesting module. This is mandatory if calling_module is 724. For other calling modules, instance_id is obtained from MRP_AP_APPS_INSTANCES. |
3. | Inventory_Item_Id: Inventory Item ID for which the ATP check needs to be done. This field is mandatory. |
4. | Inventory_Item_Name: Name of the items. If not provided, then ATP may populate this field. |
5. | Source_Organization_Id: Shipping Organization ID. This is the inventory organization that you want the ATP check performed against. If not provided, ATP calculates the shipping organization ID using sourcing rules based on provided customer_site_id/organization_id. |
6. | Source_Organization_Code: Shipping Organization Code. ATP populates this field based on Source_Organization_Id. |
7. | Organization_Id: Receiving organization ID. Either organization_id or customer_id must be provided but both should not be provided. |
8. | Identifier: Order line ID. This field is mandatory for scheduling, unscheduling, and rescheduling. |
9. | Demand_Source_Header_Id: Header ID for Order. This field is not mandatory. |
10. | Demand_Source_Delivery: This field is used along with demand_source_header_id and demand_source_type to uniquely identify an order in Order Management. This field is not mandatory. |
11. | Demand_Source_Type: This field is used along with demand_source_header_id and demand_source_delivery to uniquely identify an order in Order Management. This field is not mandatory. |
12. | Scenario_Id: This field is for ATP internal use. |
13. | Calling_Module: Module that called ATP.
|
14. | Customer_Id: ID of the customer for whom ATP check needs to be done. Either organization_id or customer_id must be provided but both should not be provided. |
15. | Customer_Site_Id: Ship to Site ID of the receiving Customer Site. If this field is not provided then ATP cannot do global sourcing and ship method/delivery lead time calculation. |
16. | Destination_Time_Zone: Time zone of the requesting organization. ATP does not support this field at present. |
17. | Quantity_Ordered: Quantity ordered for the items expressed in Quantity_UOM. This field is mandatory. For unscheduling, this field must be 0. |
18. | Quantity_UOM: Unit of measurement of items ordered. This field is mandatory. |
19. | Requested_Ship_Date: Requested ship date for the items. Either requested_ship_date or requested_arrival_date must be provided but both should not be provided. |
20. | Requested_Arrival_Date: Requested arrival date for the items. Either requested_ship_date or requested_arrival_date must be provided but both should not be provided. |
21. | Earliest_Acceptable_Date: Earliest acceptable date by which the requester is ready to accept the order in case ATP check fails on requested ship or arrival date. This feature is not used by ATP at present. |
22. | Latest_Acceptable_Date: Latest acceptable date by which the requester is ready to accept the order in case ATP check fails on requested ship or arrival date. |
23. | Delivery_Lead_Time: Delivery lead time between shipping and receiving organization. If not provided, then ATP calculates it based on ship method provided to ATP or else default ship method setup between ship-from Org and ship-to site. Customer_Site_ID must be provided for ATP to make this calculation. |
24. | Freight_Carrier: Freight Carrier used for the shipment. This feature is not used by ATP at present. |
25. | Ship_Method: Ship method to be used for shipping. If delivery_lead_time is provided then this is not required. Otherwise, ATP tries to calculate delivery_lead_time based on provided ship method. If the ship_method provided is not a valid one between the source organization and receiving organization/customer, then ATP uses the default shipping method. If the default shipping method is set between the source organization and receiving organization/customer, then ATP will assign the default ship method to this field else this field will be left empty. Customer_Site_ID must be provided for ATP to make this calculation. |
26. | Demand_Class: Demand class under which customer or requesting organization falls. This field is not mandatory. |
27. | Ship_Set_Name: Name of the ship-set. For line items, this field remains empty. Either Ship_set_name or Arrival_Set_Name should be passed, and not both. All lines in a set must be passed consecutively. |
28. | Arrival_Set_Name: Name of the arrival-set. For line items, this field remains empty. Either Ship_set_name or Arrival_Set_Name should be passed, and not both. |
29. | Override_Flag: Indicates ATP to honor the requested date irrespective of availability of the requested items. Possible values:
|
30. | Action: Type of Inquiry. This field is mandatory. Possible Values:
|
31. | Ship_Date: Date on which requested item will be shipped. This field is populated by ATP. |
32. | Arrival_Date: Date on which requested item will arrive. This field is populated by ATP. |
33. | Available_Quantity: Quantity available on ship date. This field is populated by ATP. |
34. | Requested_Date_Quantity: Quantity available on requested ship/arrival date. This field is populated by ATP. |
35. | Group_Ship_Date: Ship date for whole ship set. This field is populated by ATP in case of ship set. |
36. | Group_Arrival_Date: Arrival date for arrival set. This field is populated by ATP for both ship set and arrival set. |
37. | Vendor_Id: Vendor ID from where item needs to be requested. This field is not used by ATP. |
38. | Vendor_Name: Vendor Name. This field is not used by ATP. |
39. | Vendor_Site_Id: ID of vendor site from where item needs to be requested. This field is not used by ATP. |
40. | Vendor_Site_Name: Vendor site name. This field is not used by ATP. |
41. | Insert_Flag: Flag to indicate if supply/demand and period details are calculated or not. If this field is set to 1, then ATP calculates supply/demand and period details. Unless the user needs to see supply demand details, for performance reasons this field should be set to something other than 1. |
42. | OE_Flag: Indicates if it is an internal sales order or not. Possible values:
|
43. | Atp_Lead_Time: ATP Lead Time for Configure-to-Order Models/ Option Classes/ Option Items etc. This field is populated by ATP. |
44. | Error_Code: Error code of the error occurred during ATP check. Check MTL_DEMAND_INTERFACE _ERRORS lookup for a complete list of error codes and corresponding error messages. |
45. | Message: Error message for the error occurred during ATP check. This field is not used by ATP. |
46. | End_Pegging_Id: Pegging ID for the ultimate parent. This field is populated by ATP. |
47. | Order_Number: Order number in Order management. |
48. | Old_Source_Organization_Id: This field is used for unscheduling/rescheduling and indicates ID of Organization where item was scheduled initially. |
49. | Old_Demand_Class: Used for unscheduling/rescheduling and indicates the demand class under which item was scheduled initially. |
50. | Ato_delete_flag: Indicates if the item requested for Unscheduling is part of an ATO Model. Possible values are Y or N. This field is obsolete in 11.5.10. |
51. | Attribute_01: Used for passing source document line id for internal sales orders. |
52. | Attribute_02: Used for diagnostic ATP.
|
53. | Attribute_03: Reserved for future ATP functionalities. |
54. | Attribute_04: ATP uses this flag internally to pass refresh number in 24x7 processing. |
55. | Attribute_05: ATP uses this flag internally to pass visible demand flag for ATO items. |
56. | Attribute_06: ATP uses this flag internally to pass ATP_FLAG for an item from source to destination |
57. | Attribute_07: ATP uses this flag internally to pass back the name of the plan used by ATP for inquiry. |
58. | Attribute_08: Reserved for future ATP functionalities. |
59. | Attribute_09: Reserved for future ATP functionalities. |
60. | Attribute_10: Reserved for future ATP functionalities. |
61. | Customer_name: Name of ship-to customer entered on the sales order pad. Currently, this field is not used by ATP. |
62. | Customer_class: Reserved for future ATP functionalities. |
63. | Customer_location: Customer location of ship-to customer entered on the sales order pad. Currently, this field is not used by ATP. |
64. | Customer_country: Country of ship-to customer entered on the sales order pad. |
65. | Customer_state: State of ship-to customer entered on the sales order pad. |
66. | Customer_city: City of ship-to customer entered on the sales order pad. |
67. | Customer_postal_code: Postal code of ship-to customer entered on the sales order pad. |
68. | Substitution_typ_code: Type of substitution that should be performed on the line. Possible values:
|
69. | Req_item_detail_flag: Indicates whether ATP details of original items should be provided or not in case a substitute is used to satisfy the demand.
|
70. | Request_item_id: Source inventory item id of the requested item in case substitute is used to satisfy the demand. |
71. | Req_item_req_date_qty: Request date quantity for requested item. This field is populated by ATP only if the Req_item_detail_flag field is set to 1 and susbtitution occurs. . |
72. | Req_item_available_date: Date on which requested item is available. This field is populated by ATP only if the Req_item_detail_flag field is set to 1 and substitution occurs. |
73. | Req_item_available_date_qty: Quantity of requested item on ATP date. This field is populated by ATP only if the Req_item_detail_flag field is set to 1. This field is populated only if substitution occurs. |
74. | Request_item_name: Name of the requested item. This field is populated only if substitution occurs. |
75. | Old_inventory_item_id: Source inventory item ID for the item used during last scheduling session for the line. |
76. | Sales_rep: Name of the sales representatives listed on the order line. If this is not provided, then workflow notification is not sent in case of substitution. |
77. | Customer_contact: Name of the customer contact listed on the order line. If this is not provided, then workflow notification is not sent in case of substitution. |
78. | Subst_flag: Contains 1 if substitution occurs for the line. |
79. | Top_Model_line_id: Line ID of the top model for an ATO/PTO configuration |
80. | ATO_Parent_Model_Line_Id: Line ID of parent ATO configuration. |
81. | ATO_Model_Line_Id: Line ID of the top ATO model configuration. |
82. | Parent_line_id: Line ID of the parent item in case of ATO/PTO models. |
83. | Match_item_id: Source inventory item ID for the matched configuration. |
84. | Config_item_line_id: Line ID of the configuration item linked to a sales order. |
85. | Validation_Org: Validation organization ID for the calling instance. |
86. | Component_Sequence_ID: Sequence ID of an option item/class in the BOM of an ATO model. |
87. | Component_Code: Component code of an option item/class in the BOM of an ATO model. |
88. | Line_number: Line number of an item on sales order. |
89. | Included_item_flag: Indicates whether calling module has already exploded included items for a PTO model/Kit or not.
|
90. | Atp_flag: ATP flag for an item. This field is for internal ATP use. . |
91. | Atp_components_flag: ATP Components flag for an item. This field is for internal ATP use. |
92. | Wip_supply_type: WIP Supply type for an item. This field is for internal ATP use. |
93. | Bom_item_type: BOM item type for an item. This field is for internal ATP use. |
94. | Mandatory_item_flag: Indicates whether the item is mandatory for PTO model or not. This field is applicable only when the Included_item_flag field is set to 2. This field is for internal ATP use. |
95. | Pick_components_flag: Pick components flag for an item. |
96. | Base_model_id: Inventory item id for the base model for a matched configuration. |
97. | Oss_error_code: Code of the error encountered while evaluating option specific sourcing. |
98. | Matched_item_name: Name of the matched configuration. This field is populated by ATP in case matched ATO configuration is found. |
99. | Cascade_model_info_to_comp: Indicates whether availability result information for top ATO model should be cascaded to its components or not. Possible values:
|
100. | Sequence_number: Sequence in which items are passed to ATP for availability check. |
101. | Firm_flag: Indicates whether line has been firmed or not. This field is specifically used for Order Backlog Workbench. |
102 | Order_line_number: Line number for an item on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
103. | Option_number: Number for on option on Order backlog workbench. This field is specifically used for order backlog workbench. |
104. | Shipment_number: Shipment number for on option on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
105. | Item_desc: Description of an item on Order backlog workbench. This field is specifically used for Order Backlog Workbench. |
106. | Old_line_schedule_date: Old schedule date for a give line on Order Backlog Workbench. This field is specifically used for Order Backlog Workbench. |
107. | Old_source_organization_code: Code of an organization in which order was last scheduled. This field is specifically used for Order Backlog Workbench. |
108. | Firm_source_org_id: Code of an organization in which order was last scheduled. This field is specifically used for Order Backlog Workbench. |
109. | Firm_source_org_code: Code of the source organization. This field is specifically used for Order Backlog Workbench. |
110. | Firm_ship_date: Firm ship date. This field is specifically used for Order Backlog Workbench. |
111. | Firm_arrival_date: Firm arrival date. This field is specifically used for Order Backlog Workbench. |
112. | Ship_method_text: Ship method description. This field is specifically used for Order Backlog Workbench. |
113. | Ship_set_id: ID for the ship set. This field is specifically used for Order Backlog Workbench. |
114. | Arrival_set_id: ID for arrival set. This field is specifically used for Order Backlog Workbench. |
115. | Project_ID: ID of the project with which line is associated. This field is specifically used for Order Backlog Workbench. |
116. | Task_ID: ID of the task with which line is associated. This field is specifically used for Order Backlog Workbench. |
117. | Project_number: Project number. This field is specifically used for Order Backlog Workbench. |
118. | Task_number: Task number. This field is specifically used for Order Backlog Workbench. |
119. | Attribute_11: Reserved for future ATP functionalities. |
120. | Attribute_12: Reserved for future ATP functionalities. |
121. | Attribute_13: Reserved for future ATP functionalities. |
122. | Attribute_14: Reserved for future ATP functionalities. |
123. | Attribute_15: Reserved for future ATP functionalities. |
124. | Attribute_16: Reserved for future ATP functionalities. |
125. | Attribute_17: Reserved for future ATP functionalities |
126. | Attribute_18: Reserved for future ATP functionalities. |
127. | 127Attribute_19: Reserved for future ATP functionalities. |
128. | Attribute_20: Reserved for future ATP functionalities. |
129. | Attribute_21: Reserved for future ATP functionalites. |
130. | Attribute_22: Reserved for future ATP functionalities. |
131. | Attribute_23: Reserved for future ATP functionalities. |
132. | Attribute_24: Reserved for future ATP functionalities. |
133. | Attribute_25: Reserved for future ATP functionalities. |
134. | Attribute_26: Reserved for future ATP functionalities. |
135. | Attribute_27: Reserved for future ATP functionalities. |
136. | Attribute_28: Reserved for future ATP functionalities. |
137. | Attribute_29: Reserved for future ATP functionalities. |
138. | Attribute_30: Reserved for future ATP functionalities. |
139. | Atf_date: ATF date associated with the combined item-product family item. This field is used for internal ATP processing. |
140. | Plan_id: ID of the plan used to satisfy the demand. |
141. | Original_request_date: Original request date for the order. This field is used for internal ATP processing. |
142. | Receiving_cal_code: Code for the receiving calendar of the customer associated with the line. This field is used for internal ATP processing. |
143. | Intransit_cal_code: Code for the In-transit calendar for the customer associated with the line and the source organization. This field is used for internal ATP processing. |
144. | Shipping_cal_code: Code for the shipping calendar of the source organization. This field is used for internal ATP processing. |
145. | Manufacturing_cal_code: Code for the manufacturing calendar of the manufacturing organization. This field is used for internal ATP processing. |
146. | Internal_org_id: ID of the receiving organization in case of internal sales order. |
147. | First_valid_ship_arrival_date: If the request date type is Ship, this field contains the first valid ship date after the system date as per the shipping calendar for the source organization. If the request date type is Arrival, then this field contains the first valid arrival date after the system date as per the receiving calendar of the customer. |
148. | Party_site_ID: This field contains party site indentifier for ship-to customer site |
149. | Part_of_set: Used in the context of lines that are added to an existing set. If it is set to Y, ATP will validate the scheduled date with the date passed by Oracle Order management for the existing set. If the scheduled date does not meet the date, it will fail. If it fails, ATP removes the pegging created since leaving it might lead to dual consumption. |