Definition
An interface to update the key figures Final Actuals, Final Forecast and Distribution Factor in one or more Periods for a Material and Supply Planning Area Combination
Business Context and Use
This web service is used to maintain one or more demand plans using imported structured data.
Prerequisites
The Demand Plan has to be created and should be active in the ByDesign system.
More Information
Request Type
The request message DemandPlanBundleMaintainRequestSync contains a DemandPlan node element.
Node - DemandPlan
This is the root node for each demand plan being passed in the request. The DemandPlan node can occur multiple times in the request message; this means that multiple demand plans can be created through a single web service request. Following are the elements of this node:-
| Element |
Description |
| DEMAND_PLAN_ID |
Demand Plan Identifier created in ByDesign system |
| PRODUCT_ID |
Material ID.This field is mandatory. |
| SUPPLY_PLANNING_AREA_ID |
Site ID of the site where the material is produced. This field is mandatory. |
| TIME_SERIES_PERIOD |
Period for which the quantity is updated in YYYY-MM or YYYY-WW format |
| TIME_SERIES_QUANTITY |
Material quantity unit of measurement and quantity.This field is mandatory. |
| KEY_FIGURE_TYPE_CODE |
The Key Figure Type Code, the allowed values being 2(Final Actuals), 4(Final Forecast) and 5(Distribution Factor).This field is mandatory. |
Reponse Type
The response message DemandPlan contains two nodes:
The DemandPlan displays the following information of the created production proposal:
| Element |
Description |
| DEMAND_PLAN_ID |
The serial number specified in the request |
In addition, a log is also provided, which gives the details of errors encountered during the creation, if any.
More Information
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
Definition
An operation to update the key figures Final Actuals, Final Forecast and Distribution Factor in one or more Periods for a Material and Supply Planning Area Combination
Business Context and Use
The MaintainBundle operation is used to maintain one or more demand plans using imported structured data.
Structure
Request Type
The request message DemandPlanBundleMaintainRequestSync contains a DemandPlan node element.
Node - DemandPlan
This is the root node for each demand plan being passed in the request. The DemandPlan node can occur multiple times in the request message; this means that multiple demand plans can be updated through a single web service request. Following are the elements of this node:-
| Element |
Description |
| DEMAND_PLAN_ID |
Demand Plan Identifier created in ByDesign system |
| PRODUCT_ID |
Material ID.This field is mandatory. |
| SUPPLY_PLANNING_AREA_ID |
Site ID of the site where the material is produced. This field is mandatory. |
| TIME_SERIES_PERIOD |
Period for which the quantity is updated in YYYY-MM or YYYY-WW format |
| TIME_SERIES_QUANTITY |
Material quantity unit of measurement and quantity.This field is mandatory. |
| KEY_FIGURE_TYPE_CODE |
The Key Figure Type Code, the allowed values being 2(Final Actuals), 4(Final Forecast) and 5(Distribution Factor).This field is mandatory. |
Response Type
The response message DemandPlan contains two nodes:
The DemandPlan displays the following information of the created production proposal:
| Element |
Description |
| DEMAND_PLAN_ID |
The serial number specified in the request |
In addition, a log is also provided, which gives the details of errors encountered during the creation, if any.
Support for Extensibility:
This interface operation does not support extensibility.
Example
Request
<n0:DemandPlanBundleMaintainRequestSync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMesageHeader>
<ID>0000000000011EE18ACB68F7C79D539B</ID>
</BasicMesageHeader>
<DemandPlan>
<SupplyDemandPlanID>DP_TEST_01</SupplyDemandPlanID>
<ProductID>MCF-0001</ProductID>
<SupplyPlanningAreaID>MC64000</SupplyPlanningAreaID>
<CLOSED_DatePeriod>2013-12</CLOSED_DatePeriod>
<LARGE_Quantity unitCode="EA">27</LARGE_Quantity>
<KeyFigureTypeCode>2</KeyFigureTypeCode>
</DemandPlan>
<DemandPlan>
<SupplyDemandPlanID>DP_BP_01</SupplyDemandPlanID>
<ProductID>MCF-0001</ProductID>
<SupplyPlanningAreaID>MC64000</SupplyPlanningAreaID>
<CLOSED_DatePeriod>2013-12</CLOSED_DatePeriod>
<LARGE_Quantity unitCode="EA">28</LARGE_Quantity>
<KeyFigureTypeCode>1</KeyFigureTypeCode>
</DemandPlan>
</n0:DemandPlanBundleMaintainRequestSync>
Response
- <n0:DemandPlanBundleMaintainConfirmationSync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE5524444A11EF2F869D54:804">
- <DemandPlan>
<ChangeStateID>20131216084313.8544030</ChangeStateID>
<ReferenceObjectNodeSenderTechnicalID />
<UUID>00163e04-f8f9-1ed3-99c5-bfc95c301ed9</UUID>
<ID>DP_TEST_01</ID>
</DemandPlan>
- <DemandPlan>
<ChangeStateID>20131216084313.8544030</ChangeStateID>
<ReferenceObjectNodeSenderTechnicalID />
<UUID>00163e04-f8f9-1ed3-99c5-bfc95c301ed9</UUID>
<ID>DP_TEST_01</ID>
</DemandPlan>
<Log />
</n0:DemandPlanBundleMaintainConfirmationSync>
%CONSTRAINTS%
The Demand Plan has to be created and should be active in the ByDesign system.