Ansicht
Dokumentation

Business and Interface Objects and BAPI Methods (Changed) ( RELNAPO_401_INT_BAPI )

Business and Interface Objects and BAPI Methods (Changed) ( RELNAPO_401_INT_BAPI )

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Business and Interface Objects and BAPI Methods (Changed)

Use

This information refers to changes that were made in SAP APO 4.0 for business and interface objects, as well as the BAPIs and ALE interfaces (message types) they contain. The changes affect the following components:

  • SCM-APO-MD,,Master Data
  • SCM-APO-PPS,,Production Planning and Detailed Scheduling
  • SCM-APO-VS,,Vehicle Scheduling
  • SCM-APO-FCS,,Demand Planning
  • SCM-APO-ATP,,Global Available-to-Promise

The technical names of the objects concerned in the Business Object Repository (BOR) are as follows:

  • BUS10003 - BUS10004
  • BUS10008 - BUS10009
  • BUS10020, BUS10030
  • BUS10300
  • BUS10400
  • BUS10500 - BUS10505
  • BUS10510
  • BUS11201
  • BUS11102
  • BUS11411 - BUS11415

The associated interface objects have the same numbers, if they exist. That is, the interface object for BUS10501 is IF10501.

In particular, you should note that some interfaces have been set to obsolete. Some incompatible changes were also made, which means that some changeovers may be necessary.

Use of IDocs/ALE interfaces and function modules of BAPI methods

Changes to BAPI methods affect the associated ALE interfaces or message types. If you use IDoc message types that call the associated BAPI methods of these business objects, read the release information for the relevant BAPI methods.

Example

You are using message type SOAPS_SAVEMULTIPLE. Since this is derived from BAPI BUS10501.SaveMultiple (sales order APS), changes to BUS10501.SaveMultiple also have an effect on message type SOAPS_SAVEMULTIPLE.

In the same way, changes to BAPI methods also have an effect on the function modules used as a basis. For example, a change to method SalesOrderAPS.SaveMultiple has an effect on the function module BAPI_SLSRVAPS_SAVEMULTI.

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

New structures for characteristics: Support of IBase configurations or classifications

Previously, only CDP characteristics were supported in BAPIs. For this, one or more table parameters (for example, CHARACTERISTICS) were used in most interfaces. As of SAP APO 4.0, IBase configurations and classifications are also supported. Since these new class systems offer more functions than or different functions to CDP, new structures were created that support both IBase and CDP class systems. For information about which BAPI methods are affected by this, see the details about the individual business objects.

Enhanced transaction control

External transaction control can also be made using the COMMIT_CONTROL parameter for different write methods (for example, SaveMultiple or DeleteMultiple) of objects BUS10502 - BUS10505, BUS10505m, and BUS10300. The relevant read methods (for example, GetList) of these business objects now also support the reading of non-persistent data if, for example, a transactional simulation is open at the time of the call and the orders have not yet been posted.

New field in request methods

In these methods (for example, RequestList or RequestLoad), field ADD_APPLICATION_MESSAGES was included in parameter REQUEST_INTERFACE. This can be used to control whether messages of the "synchronous" method are to be returned in the RETURN parameter or not. For more information, see the parameter documentation of the method.

Changes that only affect certain business objects/interface objects of these components or their methods and ALE message types

Below, there is a list of new and changed business objects and BAPIs. For more information, see the documentation for the individual BAPIs.

Note that some of the BAPIs listed have not yet been released. These BAPIs may be used already, but changes may still be made that lead to compatibility problems.

If you use the associated function modules instead of BAPIs, the changes also apply for these function modules.

BUS10501 (Sales Order APS)

CreateIntransits

New methods for creating and changing orders in transit.

DeleteMultiple, RemoveItems

New parameter PLNG_VERSION for specifying a planning version. Orders from different planning versions can now be deleted.

SaveMultiple, GetList und RequestList

Methods were set to obsolete. Successor methods exist with version 2. For example, SaveMultiple2 is the successor method of SaveMultiple.

For method SaveMultiple, additional fields for account assignment were included in the parameters REQUIREMENTS and REQUIREMENTS_X. The method now allows changes to be made to additional fields.

SaveMultiple2, GetList2, RequestList2

New methods are successor methods of the obsolete versions. The main difference is that these versions use the new structures for IBASE and the CDP characteristics system.

ChangePeggingMultiple

Method was set to obsolete. The successor method is ChangePeggingMultiple of Business object PPDSServiceAPS (BUS10500).

IF10501 (Interface: Sales Order APS)

ReceiveList

Method was set to obsolete. The successor method is ReceiveList2.

ReceiveList2

New method. This method is the successor method of the obsolete version. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

BUS10500 (PPDSServiceAPS)

ChangePeggingMultiple

New method. This replaces the ChangePeggingMultiple method of the individual order objects and allows a change to the pegging between order categories. This means that you can use this method instead of having to call different ChangePeggingMultiple methods.

TransactionCommit, TransactionRollback

New methods for transaction control; that is, for posting (commit) or ROLLBACK.

BUS10502 (Procurement Order APS)

SaveMultiple, GetList und RequestList

Methods were set to obsolete. Successor methods exist with version 2. For example, SaveMultiple2 is the successor method of SaveMultiple.

For the SaveMultiple method, additional fields for account assignment data were included in parameters RECEIPTS and RECEIPTS_X.

SaveMultiple2, GetList2, RequestList2

New methods. These methods are successor methods of the obsolete versions. The main difference is that these versions use the new structures for IBASE and the CDP characteristics system.

ChangePeggingMultiple

Method was set to obsolete. The successor method is ChangePeggingMultiple of business object PPDSServiceAPS (BUS10500).

IF10502 (Interface: Procurement Order APS)

ReceiveList

Method was set to obsolete. The successor method is ReceiveList2.

ReceiveList2

New method. This method is the successor method of the obsolete version. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

BUS10503 (Manufacturing Order APS)

CreateFromTemplate

  • New field NO_DATE_FIX in parameter ORDER_HEAD. This can be used to prevent automatic fixing.
  • New field SEQUENCE_NUMBER in parameter ORDER_STRUCTURE. This can be used for subsequent heuristics or sorting, for example.

SaveMultiple, GetList und RequestList

Methods were set to obsolete. Successor methods exist with version 2. For example, SaveMultiple2 is the successor method of SaveMultiple.

SaveMultiple2, GetList2, RequestList2

New methods. These methods are successor methods of the obsolete versions. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

ChangePeggingMultiple

Method was set to obsolete. The successor method is ChangePeggingMultiple of business object PPDSServiceAPS (BUS10500).

GetList

New fields CNVIN (conversion indicator), SOURCE_TYPE, and SOURCE_NAME included in parameter ORDER_HEAD for sources of supply.

ChangeActivities

Method was released.

IF10503 (Interface: Manufacturing Order APS)

ReceiveList

Method was set to obsolete. The successor method is ReceiveList2.

ReceiveList2

New method. This method is the successor method of the obsolete version. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

BUS10504 (Stock APS)

For SAP APO 4.0, there was a conversion of the version (batch) system. This has an effect on stock methods. The main difference is that versions/batches are now separate objects that can exist independently of a stock. Business object BUS4711 (version) exists for this. This object can be used to create/change/delete versions. You can find more information about versions/batches at this object and its methods, in particular at the SaveMultiple method. Since this object does not support location dependent versions/batches, it cannot be used by stock methods.

The following settings are necessary for the use of stock BAPIs:

  • If you previously used location-dependent batches, you need to carry out a conversion and database conversion to location-independent versions/batches.
  • To ensure compatibility with previous releases, versions can only be created using the stock BAPIs (as before). However, if a stock is set to zero, the version is not deleted automatically.
  • If you use classifications/characteristics with versions/batches, the following prerequisites must also be met:
  • Versions/batches must be used.

  • The product must be assigned to a class in the product master. For CDP, this must be a class of class type 400. In addition, a class with the same name must exist with class type 230. This class with class type 230 must contain the same characteristics as the class with class type 400, although it may also contain additional characteristics.

  • Example:

The class CLASS1 (class type 400) with characteristics LENGTH and WIDTH is assigned to a product. If you are using versions/batches, a class CLASS1 with class type 230 must also be created. This class must contain the characteristics LENGTH and WIDTH, although it can also contain additional characteristics.

SaveMultiple, GetList und RequestList

Methods were set to obsolete. Successor methods exist with version 2. For example, SaveMultiple2 is the successor method of SaveMultiple.

SaveMultiple

Incompatible change: Location-dependent batches (versions) are no longer supported. This means that it is not possible to create or change location-dependent batches because there are no longer any location-dependent batches in SAP APO. A conversion or database conversion must be made to location-independent batches.

SaveMultiple2, GetList2, RequestList2

New methods. These methods are successor methods of the obsolete versions. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

SaveMultiple2

This successor method of SaveMultiple now also supports different planning versions (parameter PLANNING_VERSION) and forecast consumption with parameter FCS_REDUCTION.

IF10504 (Interface: Stock APS)

ReceiveList

Method was set to obsolete. The successor method is ReceiveList2.

ReceiveList2

New method. This method is the successor method of the obsolete version. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

BUS10505 (Order Request APS)

GetList

New fields SOURCE_TYPE and SOURCE_NAME included for source of supply in parameter ORDER_HEAD.

BUS10020 (Planned Independent Requirement APS)

New business object for planned independent requirements.

SaveMultiple

New method for creating and changing planned independent requirements.

GetList

New method for reading planned independent requirements.

DeleteMultiple

New method for deleting planned independent requirements.

BUS10030 (Vehicle Scheduling Planning Services)

GetOptimizerProfile, GetOrderSets, UnplanOrders, UpdateShipments

The methods were released.

GetOptimizerProfile

The method was extended by new fields and parameters because the optimization profile was enhanced.

TransactionCommit, TransactionRollback

New methods for transaction control; that is, for posting (commit) or ROLLBACK.

BUS10004 (Resource APS)

BlocksSaveMultiple

Incompatible change: Parameter BUSINESS_SYSTEMGROUP was renamed as BUSINESSSYSTEMGROUP.

GetBlocks

Incompatible change. The function module used as a basis for this method was changed to BAPI_RSSRVAPS_GETBLOCKS2. The main difference is that this version uses the new structures for IBASE and the CDP characteristics system.

Function BAPI_RSSRVAPS_GETBLOCKS

The function module was set as obsolete. The successor function is BAPI_RSSRVAPS_GETBLOCKS2.

GetDefinitions, GetBlocks

The methods were released.

RequestBlocks, RequestDefinitions

Parameter TRANSFER_MODE was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.

IF10004 (Interface: Resource APS)

ReceiveBlocks, ReceiveDefinitions

The TRANSFER_MODE parameter was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.

BUS11201 (Transportation Lane APS)

SaveMultiple

  • Extension of the key for the use of external procurement relationships by the fields SUBCO and CONSI. This means that these fields also have a key character if external procurement relationships are used. This affects the parameters PROD_PROCUREMENT and PROD_MEANS_OF_TRANSPORT.
  • New fields were included that are also new in master data.
  • The object is no longer locked during a transfer.
  • The time zone of the recipient/destination location is now used to determine the day (previously, this was always the UTC time zone).
  • Method was released.

RequestList

  • Parameter TRANSFER_MODE was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.
  • New fields were included that are also new in the master data.

GetList

  • New fields were included that are also new in the master data.
  • Methods were released.

IF11201 (Interface: Transportation lane APS)

ReceiveList

Parameter TRANSFER_MODE was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.

BUS10009 (Quota Arrangement APS)

SaveMultiple

  • The object is no longer locked during a transfer.
  • Methods were released.

GetList

Methods were released.

RequestList

  • Parameter TRANSFER_MODE was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.

IF10009 (Interface: Quota arrangement APS)

ReceiveList

Parameter TRANSFER_MODE was deleted. This represents an incompatible change. Since the field was not used, this does not lead to a functional change.

BUS11411 (LocSubProc APS)

New object for location determination procedures: The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11411 (Interface Object for LocSubProcAPS)

New interface object for object BUS11411. The following methods were implemented:

  • ReceiveList

BUS11412 (PrdSubProc APS)

New object for product substitution procedures. The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11412 (Interface Object for PrdSubProcAPS)

New interface object for object BUS11412. The following methods were implemented:

  • ReceiveList

BUS11413 (RuleAPS)

New object for ATP substitution rules. The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11413 (Interface Object for RuleAPS)

New interface object for object BUS11413. The following methods were implemented:

  • ReceiveList

BUS11414 (LocPrdSubProcAPS)

New object for location product substitution procedures. The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11414 (Interface Object for LocPrdSubProcAPS)

New interface object for object BUS11414. The following methods were implemented:

  • ReceiveList

BUS11415 (PPMSubProcAPS)

New object for PPM substitution procedures. The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11415 (Interface Object for PPMSubProcAPS)

New interface object for object BUS11415. The following methods were implemented:

  • ReceiveList

BUS11102 (PromotionAPS)

New object for promotions. The following methods were implemented:

  • SaveMultiple
  • GetList
  • DeleteMultiple
  • RequestList

IF11102 (Interface Object for PromotionAPS)

New interface object for object BUS11102. The following methods were implemented:

  • ReceiveList

BUS10030 (PlanningBookAPS)

Compatible extension of GetDetail method by the optional parameter ReadOptions.

Compatible extension of RequestDetail method by the optional parameters ReadOptions, CharacteristicMapping, and CharCombMapping.

BUS10002 (LocationAPS)

The following methods were set to obsolete:

  • SaveMultiple
  • GetList
  • RequestList
  • DeleteMultiple

The following successor functions were implemented:

  • SaveMultiple2
  • GetList2
  • RequestList2
  • DeleteMultiple2

IF10002 (Interface Object for LocationAPS)

The following methods were set to obsolete:

  • ReceiveList

The following successor methods were implemented:

  • ReceiveList2

BUS10001 (ProductAPS)

The following methods were set to obsolete:

  • SaveMultiple
  • GetList
  • RequestList

The following successor methods were implemented:

  • SaveMultiple2
  • GetList2
  • RequestList2

IF10001 (Interface Object for ProductAPS)

The following methods were set to obsolete:

  • ,,ReceiveList

The following successor methods were implemented:

  • ,,ReceiveList2

BUS10003 (ProdProcessModelAPS)

Compatible extension of the GetList method by the optional parameters PpmModel, MaxNumberOfPlans, and NumberOfPlans. In addition, parameters Ppm and ActivityRelation that already existed were extended.

Compatible extension of the RequestList method by the optional parameter MaxNumberOfPlans.

Compatible extension of the SaveMultiple method. For this, the parameters PpmModel, Ppm and PpmX, and ActivityRelation and ActivityRelationX were extended.

IF10003 (Interface Object for ProdProcessModelAPS)

Compatible extension of the GetList method by the optional parameters PpmModel and NumberOfPlans. In addition, parameters Ppm and ActivityRelation that already existed were extended.

BUS10004 (ResourceAPS)

Compatible extension of the GetList method by the optional parameters ResourceModel and ResourceDowntimeText. Parameter ResourceHead was also extended.

Compatible extension of the SaveMultiple method by the optional parameters ResourceDowntimeText and ResourceDowntimeTextX. In addition, the parameters ResourceModel, ResourceHead, and ResourceHeadX were extended.

Compatible extension of the ChangeMultiple method by the optional parameters ResourceDowntimeText and ResourceDowntimeTextX. In addition, parameters ResourceHead and ResourceHeadX were extended.

New method DeleteMultiple implemented.

IF10004 (Interface Object for ResourceAPS)

Compatible extension of the ReceiveList method by the optional parameters ResourceDowntimeText and ResourceModel. In addition, parameter ResourceHead was extended.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






RFUMSV00 - Advance Return for Tax on Sales/Purchases   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 24256 Date: 20240329 Time: 095245     sap01-206 ( 286 ms )