Kontakt

Ansicht
Dokumentation

APO-INT-EXT: BAPIs ( RELNAPO_30A_SP1_BAPI )

APO-INT-EXT: BAPIs ( RELNAPO_30A_SP1_BAPI )

TXBHW - Original Tax Base Amount in Local Currency   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

APO-INT-EXT: BAPIs

Use

The following modifications and extensions to the APO BAPIs are available as of Release 3.0A (First Customer Shipment and Support Package 1). They cover business objects and interface objects and the BAPIs they contain, as well as ALE interfaces (message types) from the following components:

  • APO-PPS production and detailed scheduling
  • APO-CBO general business objects (APO)

More detailed information is available in the function module documentation (se 80) for the relevant BAPI.

Changes that affect most business objects of these components or their methods and ALE message types:

Length Changes in GUIDs

The data elements for GUIDs (e.g. ORDID, ACTID, SCHEDID, RESID fields) have been changed from CHAR22 to CHAR32. A CHAR32 GUID still contains the same information as a CHAR22 GUID, but is now represented differently. A CHAR32 GUID consists of only HEX numbers in upper-case letters, whereas a CHAR22 GUID contains a compressed notation consisting of numbers and letters in both upper and lower-case (UUENCODEd). Both representations are binary in origin (i.e. CHAR16 with 128 BIT).

More detailed information on the different GUID representations is available in the GUID_CREATE and GUID_CONVERT function modules.

Logging (LiveCache Logging)

Read / write BAPIs for the BUS10501, BUS10502, BUS10503, BUS10505 and BUS10506 business objects support liveCache logging, provided it has been activated for interfaces.

Asynchronous Communication Methods

If you are using asynchronous communication methods (e.g. RequestList uor ReceiveList), please read the release information for the associated synchronous method (here: GetList). The changes described for the relevant synchronous method also apply to the asynchronous method.

Request<...>Methods

REQUEST_INTERFACE parameter

The LOGDESTSYSTEM field has been renamed EXPLICIT_RECEIVER.

The RECSYSTEM and SNDSYSTEM fields have also been added.

Receive<...>Methods

SENDER_INFORMATION parameter

The SENDSYSTEM and RECVSYSTEM parameters have been added.

Using IDOCs / ALE Interfaces

Changes to the BAPI methods also affect the relevant ALE interfaces and message types. If you are using IDOC message types that call up the associated BAPI methods of these business objects, please read the release information for the relevant BAPI methods.

Example:
You are using the SOAPS_SAVEMULTIPLE message type. Since this is derived from the BAPI BUS10501.SaveMultiple (Sales Order APS), changes to BUS10501.SaveMultiple also affect the SOAPS_SAVEMULTIPLE message type.

BUS10501 (Sales Order APS)

Changes affecting all methods of this business object:

Key Change

The sales order key has been changed from BUSINESS_SYSTEM_GROUP + ORDER_NUMBER to ORDID (=order GUID) + PLANNING_VERSION.

Access via External Key

In APO 2.0, it was possible to access an order with the BUSINESS_SYSTEM_GROUP + ORDER_NUMBER keys. This has been changed so that access is now possible via the external LOGICAL_SYSTEM + ORDER_NUMBER key.

This means that if two logical systems are assigned to one system group, each logical system now has its own number range.

For this reason, the BUSINESS_SYSTEM_GROUP field is no longer used for transaction data. The system group is determined internally from the transferred LOGICAL_SYSTEM, since it is assigned to one system group. During this conversion process, the logical system was added to many structures (if the system contained an order number).

Planning Version:

The import parameter for the planning version (PLANNING_VERSION field) has been added to certain methods. The active, operative planning version is used with methods for which no planning version can be specified.

Changes to certain business object methods:

SaveMultiple

The NO_CREATE parameter, with which you can specify whether an object is to be created if it does not already exist, has been added.

REQUIREMENTS and REQUIREMENTS_X parameter:

  • Under/over delivery tolerance and priority fields have been added.
  • The position of the ATPCAT field within the parameter has been changed.

ChangePeggingMultiple

PEGGING_INPUT_NODES parameters:

  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added. These indicate the logical systems to which the order numbers belong if the PGIN_ORDER_NUMBER or PGOUT_ORDER_NUMBER fields are to be used.
  • PEGGING_TYPE field.
    A new pegging type has been added.
    APO 2.0 only made a distinction between fixed and dynamic pegging. APO 3.0 now makes the following further distinctions in fixed pegging:
    - fixed pegging with dynamic quantity flow.
    - fixed pegging without dynamic quantity flow.
    Note: You may have to change the fixed value for the PEGGING_TYPE to specify which type of fixed pegging is required. If the invoking program is not modified, fixed pegging with dynamic quantity flow will be used.

  • The METHOD field has been added. This is used to delete either some or all pegging links between two accounts.

GetList

Additional selection parameters:

  • CUSTOMER_SELECTION: selection by customer.
  • CHARACTERISTICS_SELECTION: selection by characteristics.

REQUIREMENTS parameter:

Additional fields (e.g. delivery tolerances, priority, status).

PEGGING_INPUT_NODES parameter:

  • FLOW_QUANTITY has been added, and is used, for example, for fixed pegging with dynamic quantity flow.

The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added, which specify the logical system to which the order number (ORDER_NUMBER) belongs.

BUS10502 (Procurement Order APS)

Changes affecting all methods of this business object:

Key Change

The order key has been changed from BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE to ORDID (=order GUID) + PLANNING_VERSION.

Access via External Key

In APO 2.0, it was possible to access an order with the BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE keys. This has been changed so that access is now possible via the external LOGICAL_SYSTEM + ORDER_TYPE + ORDER_NUMBER key.

This means that if two logical systems are assigned to one system group, each logical system now has its own number range.

For this reason, the BUSINESS_SYSTEM_GROUP field is no longer used for transaction data. The system group is determined internally from the transferred LOGICAL_SYSTEM, since it is assigned to one system group. During this conversion process, the logical system was added to many structures (if the system contained an order number).

Planning Version

The import parameter for the planning version (PLANNING_VERSION field) has been added to certain methods. The active, operative planning version is used with methods for which no planning version can be specified.

Support for Stock Transfers

In APO 2.0, only orders with one receipt element (= OUTPUT node in the REQUIREMENTS parameter) could be created via procurement orders.

In APO 3.0, it is now also possible to map orders with both receipt elements (=OUTPUT node) and issue elements (=INPUT node).

Semantic Changes to the REQUIREMENTS and REQUIREMENTS_X Parameters:

In APO 2.0, the REQUIREMENTS and REQUIREMENTS_X parameter were used for receipt elements (=OUTPUT node). In APO 3.0, these parameters are used for issue elements (=INPUT node), that exist, for example, in stock transfers. In APO 3.0, the RECEIPTS and RECEIPTS_X parameters are used for the receipt elements (=OUTPUT node). It is vital that this change is noted, otherwise an issue element will be filled in APO 3.0 instead of a receipt element.

Changes affecting certain methods of the business object:

SaveMultiple

  • The NO_CREATE parameter, with which you can specify whether an object is to be created if it does not already exist, has been added.
  • More fields have been added to the table parameters.
  • Note also the semantic changes to the REQUIREMENTS and REQUIREMENTS_X parameters described above.
  • The CONF field for confirmations is no longer used. In APO 3.0, confirmations can now be mapped using a separate order type (ORDER_TYPE).
  • The ORDER_FIXED field has been renamed FIXED.
  • If you are using the function module BAPI_POSRVAPS_SAVEMULTI instead of the BAPI in APO 2.0, note that this function module is now obsolete. BAPI_POSRVAPS_SAVEMULTI2 must be used instead.
  • The PLANT parameter has been renamed LOCATION. A LOCTYPE field has also been added. Note that only the locations of the type 'Production Plant' are permitted for receipt elements.

ChangePeggingMultiple

PEGGING_INPUT_NODES parameter:

  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added. These indicate the logical systems to which the order numbers belong if the PGIN_ORDER_NUMBER or PGOUT_ORDER_NUMBER fields are to be used.
  • PEGGING_TYPE field.
    A new pegging type has been added.
    APO 2.0 only made a distinction between fixed and dynamic pegging. APO 3.0 now makes the following further distinctions in fixed pegging:
    - fixed pegging with dynamic quantity flow.
    - fixed pegging without dynamic quantity flow.
    Note: You may have to change the fixed value for the PEGGING_TYPE to specify which type of fixed pegging is required. If the invoking program is not modified, fixed pegging with dynamic quantity flow will be used.
  • The METHOD field has been added. This is used to delete either some or all pegging links between two accounts.

GetList

Addition of selection parameters:

  • VENDOR_SELECTION: selection by vendor.
  • CHARACTERISTICS_SELECTION: selection by characteristics.
  • IO_NODE_SELECTION: here you can determine whether the system is to search for products for requirement elements or receipt elements.

RECEIPTS parameter:

New parameter that provides data on receipt elements.

REQUIREMENTS parameter:

  • Provides data on issue elements.
  • Additional fields.
  • ORDER_FIXED field renamed FIXED.
  • The REL_TSTAMP field is no longer used.
  • The REQ_DATE field has been renamed DELIVERY_DATE (for receipt elements) and STAGING_DATE (for issue elements).
  • The GR_PROC_TIME field has been renamed as GI_PROC_TIME (for issue elements).
  • Note also the semantic changes to the parameter described above.
  • The PLANT parameter has been renamed LOCATION. A LOCTYPE field has also been added.

PEGGING_INPUT_NODES and PEGGING_OUTPUT_NODES parameters:

  • FLOW_QUANTITY has been added, and is used, for example, with fixed pegging with dynamic quantity flow.
  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added, which specify the logical system to which the order number (ORDER_NUMBER) belongs.

Note: The BAPI_POSRVAPS_GETLIST function module is now obsolete. Use BAPI_POSRVAPS_GETLIST2 instead.

BUS10503 (Production Order APS)

Changes affecting all the methods of this business object:

Key Change

The order key has been changed from BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE to ORDID (=order GUID) + PLANNING_VERSION.

Access via External Key

In APO 2.0, it was possible to access an order with the BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE keys. This has been changed so that access is now possible via the external LOGICAL_SYSTEM + ORDER_TYPE + ORDER_NUMBER key.

This means that if two logical systems are assigned to one system group, each logical system now has its own number range.

For this reason, the BUSINESS_SYSTEM_GROUP field is no longer used for transaction data. The system group is determined internally from the transferred LOGICAL_SYSTEM, since it is assigned to one system group. During this conversion process, the logical system was added to many structures (if the system contained an order number).

Planning Version

The import parameter for the planning version (PLANNING_VERSION field) has been added to certain methods. The active, operative planning version is used with methods for which no planning version can be specified.

Strategy Profile

In APO 2.0, the profile for R/3 integration from PP/DS Customizing for global parameters was used as the standard strategy profile.

With 3.0, a separate strategy profile exists for BAPIs, which can be entered in PP/DS Customizing for global parameters.

Changes affecting certain methods of the business object:

SaveMultiple

  • The NO_CREATE parameter, with which you can specify whether an object is to be created if it does not already exist, has been added.
  • The CHECK_PPM_EXISTENCE parameter has been added. This enables you to check whether a valid PPM exists when you create an order.
  • The STRATEGY_PROFILE parameter has been added which allows you to specify a strategy profile.
  • If you are using the function module BAPI_MOSRVAPS_SAVEMULTI instead of the BAPI in APO 2.0, note that this function module is now obsolete. BAPI_MOSRVAPS_SAVEMULTI2 must be used instead.

ORDER_HEAD and ORDER_HEAD_X parameters:

  • The PROD_LOCATION and EXPLODE_PPM fields are no longer used.
  • The MASTER_LOCTYPE field has been added. This now allows you to specify other location types for MASTER_PLANT if it is not a production plant.
  • The PLAN_NUMBER field has been added. Since the external key of a PPM has been changed, PLAN_NUMBER + PPM_NUMBER must be specified in order to clearly identify the PPM. Note that a distinction is no longer made between the internal and external PPM_NUMBER, which means that the internal APO PPM number must be transferred.

ChangePeggingMultiple

PEGGING_INPUT_NODES parameter:

  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added. These indicate the logical systems to which the order numbers belong if the PGIN_ORDER_NUMBER or PGOUT_ORDER_NUMBER fields are to be used.
  • Addition of PGIN_SCHED_LINE field.

The PEGGING_TYPE field has been added.
A new pegging type has been added.
APO 2.0 only made a distinction between fixed and dynamic pegging. APO 3.0 now makes the following further distinctions in fixed pegging:
- fixed pegging with dynamic quantity flow.
- fixed pegging without dynamic quantity flow.
Note: You may have to change the fixed value for the PEGGING_TYPE to specify which type of fixed pegging is required. If the program is not modified, fixed pegging with dynamic quantity flow will be used.

  • The METHOD field has been added. This is used to delete either some or all pegging links between two accounts.

ChangeActivities

New methods for changing the time and status of order activities.

CreateFromTemplate

New methods for creating orders on the basis of a PPM of the type template.

GetList

Additional selection parameters:

  • CHARACTERISTICS_SELECTION: selection by characteristics.
  • IO_NODE_SELECTION: here you can specify whether the system is to search for products for requirements elements or receipt elements.

ORDER_HEAD parameter:

New ORDER_SYSTEM, PARENT_ORDER_SYSTEM, PPM_NUMBER fields, as well as further status fields, for example, have been added.

Note: The length of the PLAN_NUMBER field has changed from CHAR30 to CHAR60.

ACTIVITIES parameter:

New fields added.

INPUT_NODES and OUTPUT_NODES parameters:

New fields added.

INTERNAL_CONSTRAINTS parameter:

New fields added.

PEGGING_INPUT_NODES and PEGGING_OUTPUT_NODES parameters:

  • FLOW_QUANTITY has been added, and is used, for example, with fixed pegging with dynamic quantity flow.
  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added, which specify the logical system to which the order number (ORDER_NUMBER) belongs.

ConfirmOperations

OPERATION_CONFIRMATION parameter:

The CAPACITY, CAPACITYUNIT fields, as well as CAPACITYUNIT_ISO are no longer used, since these are not supported.

BUS10504 (Stock APS)

GetList

  • The PLANNING_VERSION field has been added as a selection criterion.
  • The BUSINESS_SYSTEM_GROUP field has been deleted.

STOCK parameter:

The OWNER and OWNER_LOCTYPE fields have been added.

PEGGING_NODES parameter:

The PGIN_ORDER_SYSTEM and FLOW_QUANTITY fields have been added.

SaveMultiple

The BUSINESS_SYSTEM_GROUP field has been deleted.

STOCK parameter:

The OWNER field has been added.

RequestList

New asynchronous communication method.

BUS10505 (Order Requirement APS)

Changes affecting all methods of this business object:

Key Change

The order key has been changed from BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE to ORDID (=order GUID) + PLANNING_VERSION.

Access via External Key

In APO 2.0, it was possible to access an order with the BUSINESS_SYSTEM_GROUP + ORDER_NUMBER + ORDER_TYPE keys. This has been changed so that access is now possible the external LOGICAL_SYSTEM + ORDER_TYPE + ORDER_NUMBER key.

This means that if two logical systems are assigned to one system group, each logical system now has its own number range.

For this reason, the BUSINESS_SYSTEM_GROUP field is no longer used for transaction data. The system group is determined internally from the transferred LOGICAL_SYSTEM, since it is assigned to one system group. During this conversion process, the logical system was added to many structures (if the system contained an order number).

Planning Version

The import parameter for the planning version (PLANNING_VERSION field) has been added to certain methods. The active, operative planning version is used with methods for which no planning version can be specified.

Note: The methods for this object are obsolete. If you have been using the methods for reading transport orders, please try to use the methods for the BUS10502 object instead.

GetList

Additional selection parameters:

  • CHARACTERISTICS_SELECTION: selection by characteristics.
  • IO_NODE_SELECTION: here you can specify whether the system is to search for products for requirement elements or receipt elements.

ORDER_HEAD parameter

New ORDER_SYSTEM, PARENT_ORDER_SYSTEM, PPM_NUMBER fields, as well as further status fields, for example, have been added.

Note: The length of the PLAN_NUMBER field has changed from CHAR30 to CHAR60

ACTIVITIES parameter:

New fields added.

INPUT_NODES and OUTPUT_NODES parameters:

New fields added.

INTERNAL_CONSTRAINTS parameter:

New fields added.

PEGGING_INPUT_NODES and PEGGING_OUTPUT_NODES parameters:

  • FLOW_QUANTITY has been added, and is used, for example, with fixed pegging with dynamic quantity flow.
  • The PGIN_ORDER_SYSTEM and PGOUT_ORDER_SYSTEM fields have been added, which specify the logical system to which the order number (ORDER_NUMBER) belongs.

IF10506 IF_OrderAPSReceiver

Changes affecting certain methods of this business object:

ReceivePlanningResult

Note that in APO 3.0, Customizing for transferring events has changed. Since this method is only called if Customizing for event transfer has been maintained, the correct settings defined here are essential.

Note also that the user exit "EXIT_/SAPAPO of the extension "APOCF100" no longer exists in APO 3.0.

OBJECTS_WITH_EVENTS parameter:

The ORDER_SYSTEM field has been added.

BUS10004 (Resource APS)

Changes affecting all methods of this business object:

Key Change

The resource key has been changed from RESOURCE + LOCATION + LOCTYPE to BUSINESS_SYSTEM_GROUP + RESOURCE. For this reason, the LOCATION and LOCTYPE import parameters are no longer used with the methods for identifying a resource.

Access via External Key

In APO 2.0, it was possible to access a resource with the RESOURCE + LOCATION + LOCTYPE keys. This has been changed so that access is now possible using the external BUSINESS_SYSTEM_GROUP + RESOURCE key.

In APO 2.0, the external resource name was not mapped to the name displayed in the APO system. This is now possible in APO 3.0 thanks to a customer exit in the SaveMultiple method.

This means that every system group can transfer its resources under its own names.

Planning Version

The import parameter for the planning version (PLANNING_VERSION field) has been added to certain methods. The active, operative planning version is used for methods for which no planning version can be specified.

Changes affecting certain methods of this business object:

SaveDefinitions

New methods for creating and changing definitions.

DeleteDefinitions

New methods for deleting definitions.

GetList

Addition of new parameters:

  • PLANNING_VERSION: planning version.
  • EXCLUDE_EXPORT_FLAGS: Restrict the parameters to be returned and
    RESOURCE_DIM: dimensions of a resource, if it has several dimensions.

RESOURCE_HEADS parameter:

  • New fields added.
  • Labels for the number of takts and base rate fields have changed.

GetLoad

ORDER_HEAD parameter:

ORDER_SYSTEM field added.

SaveMultiple

  • The NO_CREATE parameter, with which you can specify whether an object is to be created if it does not already exist, has been added.
  • Exit_sapl10004_001 user exit (use of the CIF user exit no longer possible) added.
  • GUID resources have been added as an alternative key.

RESOURCE_HEAD and RESOURCE_HEAD_X parameters:

New fields added for maintaining resources.

RESOURCE_QUANMODEL and RESOURCE_QUANMODEL_X parameters:

New optional parameter for assigning a quantity / installment model to the resource.

RESOURCE_SHIFTSEQ and RESOURCE_SHIFTSEQ_X parameters:

New optional parameters for assigning a shift sequence to the resource.

RESOURCE_DOWNTIME and RESOURCE_DOWNTIME_X parameters:

New optional parameters for assigning downtime to the resource.

RESOURCE_MODEL parameter:

New optional parameter for assigning resources to models.

GetBlocks

  • CHAR_DEFINITION parameter:
  • Field name FLOAT_FROM has been changed to NUM_VALUE. The associated field type has been changed from FLOAT to QUANT 15.3.
  • Field name UNIT_FROM has been changed to NUM_UNIT.
  • Field name UNIT_FROM_ISO has been changed to NUM_UNIT_ISO.
  • Field name FLOAT_TO has been changed to NUM_VALUE_TO. The associated field type has been changed from FLOAT to QUANT 15.3.
  • Field name UNIT_TO has been changed to NUM_UNIT_TO.
  • Field name UNIT_TO_ISO has been changed to NUM_UNIT_ISO.

ChangeMultiple

New method for changing version-dependant resources.

RemoveSubobject

New method for removing assignments of quantity / installment models, shift sequences, and downtimes to the resource.

BlockSaveMultiple

New method for creating and / or changing blocks for a resource.

BUS10002 (Location APS)

SaveMultiple

Exit_sapl10002_001 user exit (use of the CIF user exit no longer possible) added.

LOCATION_HEAD and LOCATION_HEAD_X parameters:

New fields added for maintaining locations.

LOCATION_ADDRESS and LOCATION_ADDRESS_X parameters:

New optional parameter for maintaining location address data.

LOCATION_MRPAREADEF parameter:

New optional parameter.

LOCATION_MODEL parameter:

New optional parameter for assigning locations to models.

GetList

New method for extracting information on locations.

RequestList

New asynchronous communication method.

BUS10001 (Product APS)

SaveMultiple

Exit_sapl10001_001 user exit (use of the CIF user exits no longer possible) added.

PRODUCT_HEAD and PRODUCT_HEAD_X parameters:

New fields added for maintaining products.

PRODUCT_LOCATION and PRODUCT_LOCATION_X parameters:

New fields added for maintaining products.

PRODUCT_PENALTY parameter:

New optional parameter for maintaining penalty costs.

PRODUCT_LOCATION_PENALTY parameter:

New optional parameter for maintaining penalty costs.

PRODUCT_LOCATION_PRIORITY parameter:

New optional parameter for maintaining product priorities.

PRODUCT_MODEL parameter:

New optional parameter for allocating products to models.

GetList

New method for extracting product information.

RequestList

New method for asynchronous communication.

BUS10003 (Production Process Model APS)

Changes affecting all methods of this business object:

Key Changes

The PPM key has been changed from PPM_NUMBER to PPM_NUMBER + PLAN_NUMBER.

SaveMultiple

  • The PLAN_NUMBER field has been increased from 30 to 60 characters.
  • The OPERATION_NUMBER_EXTENSION field has been added to the OPERATION_NUMBER. This applies across the board.
  • Exit_sapl10003_001 user exit (use of the CIF user exits no longer possible) added.

PLAN and PLAN_X parameter:

The NO_OF_ACTIVITY field has been deleted.

PPM and PPM_X parameters:

The SOURCE_PRIORITY, DISCRETE_PPM, and BUCKET_RND_VALUE fields have been added.

OPERATION and OPERATION_X parameter:

The SETUP_ID and SETUP_KEY fields have been deleted. The SETUP_GROUP, SETUP_ITEM, STAT_SPLIT_CAPACITY, OPERATION_TYPE, and SUPER_OPERATION fields have been added.

ACTIVITY and ACTIVITY_X parameters:

The SYNCHRONIZATION field has been added.

ACTIVITY_TDPP parameter:

The PLANNING_VERSION field has been added.

ACTIVITY_TDPP_X parameter:

Parameter has been deleted.

MODE and MODE_X parameters:

  • The LOCATION and LOCTYPE fields have been deleted.
  • The BREAK_NOT_ALLOWED field has been added.

MODE_TDPP parameter:

The PLANNING_VERSION field has been added.

MODE_TDPP_X parameter:

Parameter has been deleted.

CAPACITY_REQ and CAPACITY_REQ_X parameters:

The UOM, UOM_ISO, LOCATION, and LOCTYPE fields have been deleted. The RES_CONSUMP_UOM, RES_CONSUMP_UOM_ISO, BUCKET_CONSUMP_VAR, BUCKET_CONSUMP_FIX, BUCKET_CONSUMP_UOM, and BUCKET_CONSUMP_UOM_ISO fields have been added.

CAPACITY_REQ_TDPP parameter:

  • The LOCATION and LOCTYPE have been deleted.
  • The PLANNING_VERSION field has been added.

CAPACITY_REQ_TDPP_X parameter:

Parameter has been deleted.

LOGICAL_COMPONENT and LOGICAL_COMPONENT_X parameters:

The RELATION_IO_OFFSET, IO_OFFSET, IO_OFFSEET_UOM, IO_OFFSET_UOM_ISO, IO_DURATION, IO_DURATION_UOM, and IO_DURATION_UOM_ISO fields have been added.

COMP_PRODUCT and COMP_PRODUCT_X parameters:

The AVERT_PRODUCT_EXPLOSION, PROD_CONSUMP_UOM, and PROD_CONSUMP_UOM_ISO fields have been added.

COMP_PRODUCT_TDPP parameter:

The PLANNING_VERSION field has been added.

COMP_PRODUCT_TDPP_X parameter:

Parameter has been deleted.

PPM_MODEL parameter:

New optional parameter for allocating PPMs to models.

GetList

New method for extracting scheduling and PPM information.

RequestList

New method for asynchronous communication.






CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 32867 Date: 20240426 Time: 213528     sap01-206 ( 392 ms )