Mandatory field of " version completion "indicator

Hello gurus.
I want to mandatory field of " version completion indicator to tic , when any change in purchase order in me22n, me29n.
i am waiting your reply.
regard,
riten patel

Hello Sravanthi683 .
i want to make mandatory to tic in "vesion competion" indicator field when ever change of quantity or price.
i am waiting your reply.
regard,
riten patel

Similar Messages

VERSION "completed" Indicator not restricting further GR and IR of PO

Dear SAP Gurus,
(Sorry, re-creating the Post as the earlier one was created by other user and is closed and i could not assign any points for valuable answers)
In my case the Version management is behaving in a strange manner,
I have created a PO value 1000 unit, and got it released,
now change the value to 2000 it asks for version management i fill the Reason and Text field at Version Management TAB, the system is not asking me to Mark the Version completed indicator ( it is not a mandatory field)
but my biggest issue is even though the Version Completed Indicator is not Ticked the PO could be used for subsequent process,
there can be GR made for this PO, and also Invoice made for the same PO,
system is allowing further processing of the PO where VERSION "completed" Indicator is not ticked.
Please guide if there is any Config to restrict the PO where VERSION completed Indicator is not ticked from going to GR and IR,
( as per the previous posts i also feel making VERSION completed Indicator as mandatory field is not a best Practice, as it will cause new version for small changes in PO)
Thanks and Regards
S Kumar

Hello,
Thanks for ur reply,
Yes we have release stratergy implemented, and our release is also not reset until we tick the version Completed Indicator,
This is really making the system vulnerable as people can make any changes to Qty and Value and neither the system is asking for New version nor resetting the existing Release,
and people can use the PO for Making GR and IR as well, which is not acceptable.
Please guide if any Config is missing to check the same,
Thanks and Regards,
S Kumar

Userexit for Version completed indicator to make Mandatory

Dear Experts,
We want to have field u201CVersion completed indicator u201C to be Mandatory in ME22N Transaction,Please suggest which User exit Or BADI we can use do this ?
Thanks

Please check user exit EXIT_SAPMM06E_017 in enhancement MM06E005 (tcode SMOD).
u can also use the Badi for the po. Purchase order Badi is ME_PURCHDOC_POSTED
Additionally check
SPRo->MM>Purchase order->define screen layout for document level->ME22>check here if version mgt is active

Delivery Completed Indicator - Open PO Quantity Issue

Hi All,
I have an issue relating to our Open Purchase Order Report. I have some POs which are appearing on the report eventhough they are marked, 'Delivery Complete' ie NOT open. The example of a PO is where the PO Quantity is 100 and the Goods Receipt is 99. The user knows that there will be no further deliveries and therefore marks the PO 'Delivery Complete'
In the Extractor to BI we have extracted this field ELIKZ 'Delivery Completed Indicator'. The structure of our datamodel is
PSA -> DSO (Write Optimised DSO) -> Cube
We calculate the Open PO Qty by taking 'PO Qty' minus 'Goods Receipt Quantity' I have checked the example PO in the cube & DSO. I can see that for the infoobject 'Delivery Complete Indicator' that it has been marked 'X' but only on the records relating to the Goods Receipt for this PO. The original PO record is added to the cube eg on 1st Jan and then the Goods Receipt record, including the delivery complete indicator is added to the cube on 31st Jan, but the original record is not updated by this indicator. Therefore at the moment I cannot use this to filter out records in my query. See below how it looks in the Cube;
Created Date - PO No - PO Line - Del Complete Indicator - PO QTy - Goods Receipt Qty
01.01.2011 123 10 (Blank) 100
31.01.2011 123 10 X 99
What should I do? How have you created this report?
Just to let you know I have already read the post Delivery Completed Indicator(ELIKZ:0COMPL_DEL) in 2LIS_02_SCL
Many thanks for your help,
Michelle

Hi Kalyan,
Thanks very much for your message,
In my case if the Order Qty is not equal to receipted this does not always mean that it is open. Sometimes the receipted quantity can be over or under (not equal) and the PO can be closed. What do you mean by confirmed quanity? Also, this is a Purchase Order report not a Sales report.
You have said...
"Then I would suggest to still keep the condition on the Net ord qty and Net confirmed qty and exclude the del compl indicator as X and also the status as open "
I don't understand how this will work. My issue is that the indicator is not on all the records of a PO only the receipted records.
Can you help again please?
Many thanks
Michelle

Service completion indicator

Dear Experts,
I know there is the field for Delivery completion Indicator for std PO's..
After that we cannot receive any further materials against that PO. (Delivery Tab)..
But for Service PO.. the delivery completion indicator is not avl.. please let me know.. to close the PO for service...
Pls guide me.. urgently.. thanks

Hi
At the time of service entry sheet set the status as Final entry (Ctrl + F5)
This will close the PO for further services.
Thanks & Regards
Kishore

How can you ensure all mandatory fields are filled, before pressing the submit button?

Hi all,
I've got a complex form with many different pages (17 so far) and I'm using visible/hidden to change the layout so only 1 page appears at a time.
What I want to do is have a better check for what mandatory fields have not been filled out in my form. The submit buttons checks that all of the mandatory fields have been completed, but if that's 1 field on page 1, searching through my entire document would cause the users to lose the will to live!
I am after either returning more meaningful information to the user when a submit fails, or being able to run the mandatory check field every time the page changes. I already dynamically set most of the mandatory fields according to what is/isn't visible so adapting my form wouldn't take long but I have no idea how to get it to check if all the fields have been filled in.
Many thanks,
Tom

Right, I have pretty much all of my validations working now... and here's the word you're waiting for... but, I am having a problem with fields that are already visible when the rest of the layout changes.
Basically, one of the options above the field with the problem is being changed, which makes the layout above that field change. This is triggering the validate event.
This wouldn't stop anyone using my form, but it is an annoyance.
Anyone able to help?
Many thanks,
Tom

VERSION "completed" check box to be made mandatory

Sir,
I want to make version "completed" check box to be now made mandatory.
right now reason and text is made mandatory
regards
amey

When you create a requisition or an external purchasing document (such as a PO), the system automatically creates an initial version (version 0). From this time on, changes and newly entered data are documented in the current version that is valid in each case.
In the case of requisitions, one version is generated per requisition item (at item level). In the case of external purchasing documents, one version is generated per document (at header level).
Once all necessary data has been entered for the purchase requisition, the version must be completed. Only then can:
● The purchase requisition be released or converted into a follow-on document
If a requisition is subject to an overall release procedure, the versions of all requisition items must be completed in order for the requisition to be released and converted.
● The external purchasing document be released or outputted (printed out or transmitted as a fax or EDI message etc.)
You complete a version by setting the Completed indicator in the version data. The processor of a purchase requisition or external purchasing document thereby explicitly indicates that he or she has now made all changes desired at the time.
You can specify that version 0 is to be completed automatically in Customizing for Purchasing. To do so, set the Version 0 OK indicator under Version Management ® Set Up Version Management.

Version management complete indicator

Dear All ,
       I want to make version management complete indicator compulsory while saving any changed PO .That means While I am changing any PO a new version is created . If I am not putting tick in complete indicator of version and saving , it is not going for release .
        I want system should promt error if I am not completing the indicator in PO and saving OR system should not allow me to do goods receipt if the version is not complete OR I want system should automatically complete the version like there is a provision for version 0 .
         Please kindly let me know how I will accomplish any of my goal .
Regards
Abhijit

Dear Abhijith,
Check if there is any BADI for this to force the user to select the version completed check box in the purchase order.
Regards
M P D Kamath

Mandatory field is completely coloured

Hi Friends,
We have upgraded from 5.2 to 7.0. We have an Account Plan and it has various Mandatory fields marked with a star. Now the problem is for one of the mandatory field apart from the star we have a red colour covered for that particular field. Now we need to remove that red colour to that field. Kindly give your thoughts on the same.

Hi Jaya Pal,
 The red borders will stay as long as the mandatory fields are empty. This behaviour is hardcoded as part of the input field rendering. If you absolutely must eliminate this behaviour, you can try modifying a CSS file. Open BSP application thtmlb_styles in SE80. Expand Mimes->sap_skins->default and edit thtmlb_stand.css. Look for a section like this and change it as you see fit.
/* <thtmlb:inputfield> tag Mandatory field */
.th-ip-sp-md .th-if,
input.th-ip-sp-md {
 border-color: red !important;
Regards,
Arun Prakash

Mandatory fields for delivery, GI BAPIs

Hi Folks,
scenario, i have an STO number for which i have to create an outbound delivery(like its done in VL10B). now that i have a delivery number, next i have to change the quantity of this delivery and post goods issue. after GI i need to post a GR. data is comming in from a non sap system.
bapis are -
BAPI_DELIVERYPROCESSING_EXEC
to create an outbound delivery
BAPI_OUTB_DELIVERY_CHANGE
to change the outbound delivery and then post GI
BAPI_GOODSMVT_CREATE
to creat GR
can anyone who has worked with the following bapis tell me what the mandatory fields are in each bapi. i am unable to post them. i would appreciate your help and thanks in advance.

Sample Code for BAPI_GOODSMVT_CREATE
Populate header data
Posting date
 x_goodsmvt_hdr-pstng_date = <deldate>.
Document date
 x_goodsmvt_hdr-doc_date = <doc_date>.
User Name
 x_goodsmvt_hdr-pr_uname = <ernam>.
User Name
 x_goodsmvt_hdr-ref_doc_no = <PO/Delivery No).
Bill of lading
 x_goodsmvt_hdr-bill_of_lading =<BOL>.
Populate item data
Purchase order number
 i_goodsmvt_item-po_number = ebeln.
Line item number
 i_goodsmvt_item-po_item = ebelp.
Plant
 i_goodsmvt_item-plant = werks.
Movement type
 i_goodsmvt_item-move_type =movtype.
Movement indicator
 i_goodsmvt_item-mvt_ind = mvt_ind.
GR quantity
 if p_movtype = c_101.
 i_goodsmvt_item-entry_qnt = menge.
 else.
 i_goodsmvt_item-entry_qnt = menge * -1.
 endif.
GR UOM
 i_goodsmvt_item-entry_uom = meins.
Storage location
 i_goodsmvt_item-stge_loc = lgort.
Production date
 i_goodsmvt_item-prod_date = doc_date.
Delivery completion indicator
 i_goodsmvt_item-no_more_gr = c_x.
Movement Reason
 if p_movtype = c_122.
 i_goodsmvt_item-move_reas = c_12.
 endif.
endloop.
For each PO create a GR document
if not i_goodsmvt_item[] is initial.
 call function 'TRANSACTION_BEGIN'
 importing
 transaction_id = l_trans_id.
 call function 'BAPI_GOODSMVT_CREATE'
 exporting
 goodsmvt_header = x_goodsmvt_hdr
 goodsmvt_code = x_mvt_code
 importing
 materialdocument = l_mat_doc
 matdocumentyear = l_mat_doc_year
 tables
 goodsmvt_item = i_goodsmvt_item
 return = i_bapireturn.
endif.

GR after "Delivery Completed" Indicator was Set and Automatic PO Closing

Hi All!
In our system, we can still post goods receipts even if the "Delivery Completed" indicator was already set in the PO. Is there something we need to configure so as not to allow goods receiving for such POs?
Also, can we set the PO to close automatically after reaching its "Validity End"?
Please we would appreciate any suggestion for this issues.
Thanks in advance!

Hi,
The Solution is to
Reduce the PO quantity or the block the item on the PO to prevent any further GR's.
Block the purchase order item.
(ME22N: Block pushbutton; ME22 Menu -> Edit -> Block)
Fill the date field for the 'Latest Possible Goods
Receipt' (LEWED) in the purchase order item. If you do
this and you enter a GR document after this date, the
system issues message M7163, which you must set as an
error message in Customizing.
Refer to OSS note - 856279
Here is the copy
Number 856279
Version 3 from 24.06.2005
Status Released for Customer
Set on 24.06.2005
Language EN
Master language DE
Short text MIGO: Proposed qty despite 'delivery completed'
indicator
Responsible SAP AG
Component MM-IM-GR-PO
Goods Receipt from External Procurement
Regards
Kedar Kulkarni

Mass setting of delivery completed indicator

Hi,
The delivery completed indictor has not been set as a mandatory field in SPRO settings for one of the Plants.
Now,is there any transaction code or, program which can be used to set the delivery completed indicator in that Plant when the PO qty. becomes equal to the GR qty.
Please advise,
Thanks,
Kaveri

Hi Kaveri,
You could set the plant's material masters to a purchasing value key that has an under-delivery tolerance of 0%. This setting only affects the plant that uses these materials. Next, you can do the same for text purchase items by material group in the IMG path: Materials Management -> Purchasing -> Material Master -> Entry Aids for Items Without a Material Master. This would affect all plants in the same client.
What this will cause to happen, is at GR the DCI will be checked when the GR quantity equals the PR quantity and not before.
Just another way you could do it if it suits your business process and you only want the DCI if the quantities are equal.
Regards

How to validate incoming messages with mandatory field coming as null/empty

Hi,
I want to validate the incoming messages received by the file adpater.
1. Need to check that all the mandatory fields(minoccurs=1) has values, else it should return fault. But what happening now is even though the mandatory fields are empty/null, file is being read by the file adapter and not getting faulted.
2. I have tried using the Validate Activity/Assign Activity but this is a business fault and not sytem fault, hence no faults are auto generated.
3. We are presently using the if/switch activity and putting the conditions manually in order to validate the mandatory fields and hence it is throwing the business faults explicitly.
4. But if there is 200 fields mandatory out of 500 fields schema, then we need to hardocde manually all 200 fields. Please advise me if this is possible in any dynamic way.
Thanks
Edited by: 902781 on 15.mar.2012 07:33

Dear vijay,
This is my xsd::
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="exampleElement">
<xsd:annotation>
<xsd:documentation>
A sample element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
*<xsd:element name="element1" type="xsd:string" minOccurs="0"*
nillable="false"/>
*<xsd:element name="element2" type="xsd:int" minOccurs="0"*
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I tried the above xsd as well as
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="exampleElement">
<xsd:annotation>
<xsd:documentation>
A sample element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
*<xsd:element name="element1" type="xsd:string" minOccurs="1"*
nillable="false"/>
*<xsd:element name="element2" type="xsd:int" minOccurs="1"*
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
But instance is getting completed even though the mandatory string field(element 1) is empty/null like:
<element1></element1>
What I feel is, string will accept all the values whether it is int, date, long and in the same way it is accepting null character.
Please let me know if you have any solutions to overcome this.
Thanks again.

What are the Mandatory Fields in Transaction ME51

Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIV

hi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena

Deliver completed indicator is not getting updated in the PO item Overview

Hi Gurus,
We have the PO with quantity of 10 and it has been GR/IR, but the Delivery completed indicator is not getting updated (Checked).
The deliver completed indicator is selected in the config of t-code OMCD.
Also there is no tolerance limit is maintained.
Could you please suggest us why the indicator is not getting updating.
Thanks & Regards,
Sada

Hi check follwoing
1. Set Delivery complete indicator at plant leve
spro - mm --inventory mgmt ---Goods receipt --- Set delivery complete indicator
2. Control field selection for MIGO to disable users from changing it.
spro -- Materials Mgmt -->Inventory Mgmt -- Settings for enjoy Transaction -->Field Selection for MIGO
and chek this link
["Delivery Completed" Indicator
Regards
Kailas Ugale

Mandatory field of " version completion "indicator

Similar Messages

Maybe you are looking for