FAQ Mass Changes in Purchasing
Uploaded by
harperFAQ Mass Changes in Purchasing
Uploaded by
harper2019-09-13 501853
501853 - FAQ: Mass changes in purchasing
Version 13 Type SAP Note
Language Anglais Master Language Allemand
Priority Recommendations / Additional Info Category FAQ
Release Status Released for Customer Released On 29.12.2017
Component MM-PUR-GF-MAS ( Mass change )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 501853
Symptom
This SAP Note contains a list of frequently asked questions about "Mass
maintenance in purchasing".
Questions:
1. Why can certain fields not be changed using transaction MEMASSPO, or which
fields can be changed?
2. When you want to change any field of a scheduling agreement using
transaction MEMASSSA, the system issues error message MEOUT019:
"Scheduling agreements with time-independent conditions are not supported".
Why?
3. Why can info record fields be deleted using transaction MEMASSIN even
though they are defined as required entry fields?
4. Is it possible to set the deletion indicator in transaction MEMASSRQ as a
field that can be changed?
----------------------
1. Question: Why can certain fields not be changed using transaction MEMASSPO, or
which fields can be changed?
Solution: The function module ME_LIMIT_FIELDS_PO_BAPI basically contains all
nonchangeable fields for the mass change of the purchase order. In addition, the
following item fields cannot be changed with existing items:
Material number (EKPO-EMATN)
Material short text (EKPO-TXZ01)
Order quantity (EKPO-MENGE)
Order unit (EKPO-MEINS)
Net order price (EKPO-NETPR)
Purchase order price unit (EKPO-BPRME)
Plant (EKPO-WERKS)
As of SAP R/3 Release 4.6C, you can run the mass maintenance using the
PurchaseOrder.Change method (BAPI_PO_CHANGE). To do this, read SAP Note 545754.
------------------------------
2. Question: When you want to change any field of a scheduling agreement using
transaction MEMASSSA, the system issues error message MEOUT019: "Scheduling
agreements with time-independent conditions are not supported". Why?
Answer: Read FAQ note 1046794, question 1.
© 2019 SAP SE or an SAP affiliate company. All rights reserved 1 of 3
2019-09-13 501853
------------------------------
3. Question: Why can info record fields be deleted using transaction MEMASSIN even
though they are defined as required entry fields?
Answer: The mass maintenance of info records does not take the field selection
into account. It is possible to change fields that cannot be changed in dialog
mode.
------------------------------
4. Question: Is it possible to set the deletion indicator in transaction MEMASSRQ
as a field that can be changed?
Answer: In transaction MASSOBJ, you can assign the deletion indicator as an
additional field to the object type BUS2105. Call transaction MASSOBJ and select
the object type BUS2105. Now add the field list of the object type BUS2105 by
inserting an additional entry with the field name LOEKZ in the table.
As of Release ECC 6.0 EHP 4 (i.e. SAP_APPL 604), this function is provided.
------------------------------
Other Terms
Purchase order, MEMASSPO, MASSEKPO, MASSEKKO, ME_LIMIT_FIELDS_PO_BAPI, BUS2012,
MASS_CHANGE_PURCHASE_ORDER, MASS_CHANGE_PURCHASE_ORD_BAPI,
info record, MEMASSIN, BUS3003, ME_LIMIT_FIELDS_INF, MASS_INFREC01_CHANGE,
scheduling agreement, MEMASSSA, BUS2013, BAPI_SAG_CHANGE,
MASS_CHANGE_SCHED_AGREEMENT,
contract, MEMASSCONTRACT, BUS2014, BAPI_CONTRACT_CHANGE, MASS_CHANGE_CONTRACT,
purchase requisition, MEMASSRQ, BUS2105, ME_LIMIT_FIELDS_RQ,
MASS_CHANGE_PURCHASE_REQ,
MASS, EIMASS, MASSOBJ
Reason and Prerequisites
Solution
Software Components
Software Component Release
SAP_APPL 45A - 45B
SAP_APPL 46A - 46B
SAP_APPL 46C - 46C
SAP_APPL 470 - 470
© 2019 SAP SE or an SAP affiliate company. All rights reserved 2 of 3
2019-09-13 501853
SAP_APPL 500 - 500
SAP_APPL 600 - 600
SAP_APPL 602 - 602
SAP_APPL 603 - 603
SAP_APPL 604 - 604
SAP_APPL 605 - 605
SAP_APPL 606 - 606
SAP_APPL 616 - 616
SAP_APPL 617 - 617
Dieses Dokument referenziert auf
SAP-Hinweis/KBA Titel
727838 MEMASSPO: Field RETPO cannot be changed
557702 FAQ for mass maintenance
545754 Change MEMASSPO from batch input to BAPI
1046794 FAQ: BAPI for outline agreement
Dieses Dokument wird referenziert von
SAP-Hinweis/KBA Titel
2038763 MEMASSPO: why specific fields cannot be changed via MASS tools
2736422 Mass removal of Contracts / Prevent a large amount of contracts from being used anymore
