Legal control for Purchase orders / Foreign trade requirements for MM

We make parts that are military related and we must comply with the US ITAR regulations.
As part of this regulation when we buy components to make our finished goods, the vendors that we buy raw materials from must also be ITAR compliant.
Has anyone been able to do before in SAP by somehow linking a legal requirement to a PO and vendor to see if they comply and if not it blocks the PO or receipt? Can it be done in R/3 or is this something that is handled in Global Trade Services??
Any and all help is greatly appreciated!!
Debbie

Hi Debbie
Are you using QM also ? Then you can do this within standard config & master data in 3 steps:
1) You can define 'ITAR' as QM Infosystem.
IMG->QM->QM in Logistics->QM in Procurement->Define QM Systems (Txn OQB7)
Read the IMG documentation here which is good.
2) Txn:MM01. Maintain QM view for material (QM Proc active and Target QM system)
3) Txn: XK01/XK02; Maintain vendor's QM system in Purchasing data.
    OR
    QI01/QI02: You can also maintain Quality Info record for vendor/material/plant
    combination and maintain a QM system there.
You do not need to use QM additional functionalities or implement QM entirely to use this.
Best regards
Ramki

Similar Messages

Badi or Enhancement for Purchase order invoice plan change for ME22N

Hi ,
I have a req to have a custom tab at the header level with the push button in ME22N , By clicking the push button i need to update the invoice plan detail to all item level by using the 1st line item invoice paln entered while creating PO . I have done with adding the custom tab using MM06E005 enhancement. The problem i am facing is need to change the PO invoice plan detail for all line item. Please let me know the BADI or Enhancement to change the PO detail in the Tcode ME22N . Any Badi before save or after save with invoice plan details.
<offer removed by moderator>. Many thanks for you help!
Regards,
Vinoth.v
Edited by: Thomas Zloch on Oct 14, 2011 11:59 AM

Hi Eduardo
ME_PROCESS_PO_CUST is don'tt have the Invoice plan and ME_GUI_PO_CUST is for screen but i need the badi to get the invoice plan details and change the remaining item with the invoice plan .
Regards

Settings for Purchase Order output using services for MM-SUS scenario?

Dear Gurus,
I am configuring the service procurement classic and plan driven procurement for MM-SUS
environment. We are on SAP SRM 7.01/ECC 6 EHP5.
I need to maintain the below settings for PO output:
1. RUN transaction SWETYPV
2. IN the object types field, enter CL_SE_PUR_WF_OUT.
3. In the event field, enter CREATED.
4. In the receiver type field, enter WS53800008.
5. In the receiver function module field, enter SWW_WI_CREATE_VIA_EVENT_IBF.
6. Select the 'Linkage Activated' checkbox.
7. Save your entries.
Similarly, one more entry for the event CHANGED.
However, the system is not allowing me to save the settings.
If I choose BOR Object Type 'CL_SE_PUR_WF_OUT', it gives an error message 'Object type CL_SE_PUR_WF_OUT is not defined'.
If I choose object category 'Business class for object type CL_SE_PUR_WF_OUT, it gives an error message 'Class CL_SE_PUR_WF_OUT is not a business class.'
There are similar entries in the table SWETYPV for object type CL_SE_PUR_PO_WF_OUT' with object category CL.If we copy the entries and tries to replace the
object type 'CL_SE_PUR_PO_WF_OUT' with CL_SE_PUR_WF_OUT and save it, it gives an error message 'CL is not used for workflow event'.
Could you please help me on how to configure the settings for PO output from ECC system using services?
Any input is highly appreciated.
Thanks and regards,
Ranjan

Hi Ranjan,
Please add the value 'CL' in the table SWF_CATIDS
Then it will work.
With Regards,
Malay

Workflow for Purchase order

Hi,
Can anyone let me know the steps to activate workflow for purchase order so that workflow will be triggered after creation of PO and for any modification done after release.
What are the customization and tcodes required for PO workflow and is there any technical involvement requires.
Thanks in advance!
Karun

Hi
I took it from sdn.
WORKFLOW FOR PO RELEASE PROCEDURE
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users

Release Procudure for Purchase Order

Hi Experts,
I am new Release Procudure.My client wants release procedure for two users.
End user wants create Purchase Order then other user wants release that purchase order and then another user wants final release. Please tell how can map this process in sap.
Thanks in advance,
Chandhu
Edited by: chnadu9 on Jan 5, 2011 5:48 AM

Hi,
The release code is a two character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
An example of configuring a Purchase Order Release Strategy
If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
Steps for configuring the PO release strategy
Create the PO Characteristic
Transaction code : CT04 - Create Characteristic e.g. NETVALUE
Click Additional data tabstrips
Table name CEKKO Field name GNETW and press enter and you will see this information message :-
Format data taken from Data Dictionary (press enter)
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data tabsritps (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >=10000 (equal or greater than 10000) and press enter
Save your data
Create the Class of the PO Release Strategy
Transaction code : CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create button
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the class
Save your data and this message will appear :-
Class type 032: Class REL_PUR created
Define the Release Procedure
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Save your entries.
Release codes - New entries
Grp Code
02 01
Save your entries.
Release indicators - New entries
Release indicators Release Description
0 Blocked
1 X Release
Save your entries
Release Strategy - New entries
Release group 02
Rel.strategy 01 - Release
Release codes 01
Release status 0 - Blocked
1 - Release
Click the Release prerequisities button
Click the Relase statuses button the click the Continue button
Click the Classification button
Choose your check values
Click the Back button
Save your entries
Check your PO release configuration
Finally, check your PO Release Strategy configuration to make sure that there are no errors.
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Mohar

Email Alert for Purchase Order Release

Hi,
When a PO is subject to release I would like an external email to be sent to the relevant user as per assignments in config.
I have used standard workflow for PO release and this is working with no problems, alerts successfully going to the workflow inbox.
But does anyone know the steps to configure the standard workflow so that an external email is sent?
Thanks

hi
WORKFLOW FOR PO RELEASE PROCEDURE
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
regards
KI

Define Release Procedure for Purchase Orders

Hi Friends,
We are changing Release procedure for purchase orders for one department from > $ 5000 to > $ 10000.
We defined three characteristics for the class namely Purchasing Order Document, Purchasing Order Type and Ner Order Value which is Currency data type. I Defined Release Procedure for Purchase Orders in configuration master. It's working fine, I mean the Net order Value field is updated in Configuration Client.
After transporting the above change to the Testing Client, the Net Order Value field did not update in testing Client even though I created Characteristics in Testing Client (as characters are not transportable, I created them seperately in Testing Client). I can't update the Net Order Value manually in Testing Client as it says "Client 010 (test) has status 'not modifiable' "
Please tell me how to update that field, as the net order value didn't change even after transport. I can't change manually in testing Client as the status is "not modifiable"

Hi,
Yes I have already done that.
In SPRO,
After hitting the following:-
MM --> Purchasing --> Purchase Order --> Release Procedure for Purchase Orders --> Define Release procedre for Purchase Orders
I have to process the objects in the following sequence,
Release Group, Release Code, Release Indicator, Release Strategy & Workflow.
Upto Release Indicator it is fine. After hitting Release Strategy, I should select the release strategy (which I just created) and display. Then 4 buttons will be displayed namely,
Release Prerequisites, Release statuses, Classification, Release simulation.
Upto Release statuses it's fine. Afeter hitting Classification,
the values of Purchase document & Order type are populated, but the Total Net Order Value is Blank. It is supposed to populate the amount & 10,000. But it is not.
Actually that amount will be stored in the field GNETW of table CEKKO. But CEKKO is a Structure not a table. So I can't update the field.
Please advice me...
Thank You,
Nag

User Exits for Purchase order & requistion to control Material description

Dear Experts,
I am creating a Purchasing requisition & Purchase order for certain Material Type. Currently user can change material description at item level without anu check. Now I have different material type like PACKING(ZPAC), Raw material(ZROH) Etc.
My requirement is like such that i want to allow change of material description of packing material(ZPAC) but system should not allow for Raw material type(ZROH). so from where i can control this?
Can any one give me EXIT name or enhancement point for Purchase order & requisition.
Thanks in advance.
Regards,
Piyush

Dear,
You can achieve this by Field selection in SPRO > MM > Purchasing > Purchase Requisition > Define Document Types > Here get the Field Selection Key for PR Doc Type
SPRO > MM > Purchasing > Purchase Requisition > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Similarly do for PO also SPRO > MM > Purchasing > Purchase Order > Define Document Types > Here get the Field Selection Key for PO Doc Type
SPRO > MM > Purchasing > Purchase Order > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Note: - But in case of text Purchases, you need to create a new PR and PO Document Type. So that this config. will not have any impact on Text Purchases.
Regards,
R.Brahmankar

BADI requirement for Purchase Order

Hello,
I have to find a BADI for Purchase order which will satisfy requirement stated below.
When processing on PO will be done for Goods received and/or Final delivery and/or Final invoice , I need to trigger an Idoc from BADI which will inform another client that flags stated above are set against that PO.
Which BADI can be used to find information of these flag are set on PO as soon as it is processed and which in trun help me to trigger this idoc?
Regards,
Madhura

try with MB_DOCUMENT_BADI
this BADi will get trig for all goods movement transaction.
better u go for user exits, insteed of BADi

Authorization Object for Purchase order Message control

Hi ,
Is there any stadard authoriztion object to control the print and print preview options for Message control .
I am requied to control the print and print preview options for purchase order messages for certain users depeding on there authorizaion.
Thanks in advane.

Hi,
When you click on the 'print preview' button on ME22N/ME23N the system
makes an authority check on transaction ME9F activity 04. The current
logic forces the print preview functionality to be accessed ONLY by the
users who print. Therefore, only users that have authorization to use
ME9F are authorized to use the Print Preview button in ME22N/ME23N.
Kindly try the authorization objects M_BEST_EKG, M_BEST_BSA and
M_BEST_EKO = 04.
You can
also have a look the user exit
EXIT_SAPLMEDRUCK_001 in enhancement LMEDR001 for print program
SAPLMEDRUCK.
INCLUDE ZXM01U04
you can create own coding for all possible AUTHORITY-CHECK.
BR
Nadia Orlandi

Require Standard DataSources for Purchase Orders

Hi,
Please provide me the standard datasources for purchase orders to get the data updated automatically in a BI System.
I have to display report containing the purchase orders details of each day.
Regards
Sunil Kumar

Hi,
Following link will give you complete details of purchase order deports and data sources.
http://help.sap.com/saphelp_nw70/helpdata/en/df/cfb839f6a7a307e10000000a11402f/frameset.htm
Regards,
Vishnu

Seeburger help required for Purchase Order,Dispatch Advice,Supplier Invoice

Dear All,
I wanted to do the Seeburger implementation.
I wanted to convert the EDIFACT to XML struture and XML struture to EDIFACT using the seeburger adpater for --
Purchase Order , Dispatch Advice and Supplier Invoice.
Points:
1. How will vendor will send and receive data to PI. (means how to use Seeburger spoke and how to give unique Ids in Seeburger AS2 adapter)
2. How to do Edifact to XML conversion and XML to Edifact conversion using Mapping Designer
3. How to configure modules in Seeburger AS2 adapter
Regards

HI,
For Seeburger implementation you should take licance for BIC MD and Adapters(AS2,SFTP).
1)You will receive the data from the vendor ,you need to configure the AS2 Sender Adapter and you need configure the Party with AS2ID(Global Indentfier).
2)For Conversion for the EDIFACT to XML you need to generate the the BIC mapping In BIC MD.once generate the map you can loaded the map into XI server.you need to configure the mapping detials in module(Classifer,BIC,Spliter......).
Steps to genrate the BIC MAP:
Steps :-
      1) Right click on Data type and Export structure (msg_....xml).
      2) Run u201CCreateXMLmessageu201D, (source file msg_....xml, target file XML_....xml).
      3) Import XMLu2026.xml to your Project XML Message.
      4) Run u201CCreateMappingXMLToEdiu201D source file (msg_...xml),target file      (X2E_....xml)
      if you are converting XML to Edi format.
      5) Run u201CCreateMappingEdiToXMLu201D source file (msg_....xml),target file      (E2X_....xml) if you are converting Edi to XML format.
      6) Import X2E/E2X_.....xml to your project mappings
3) you need to open firwall from the vendor and your system..
AS2 Sender Adapter:
Transpoert protocl:HTTP
Message Protocol:AS2
Authincation Requered(Check box)
Message subject:
Asynchorns MDM Settings:
Server Certifacte:
Private key:
HTTP TimeOut:
MDM retry interval:
MDM retry Count:
Proxy Server:
Proxy prot:
Proxy User and Password.
For more information end to end :above menation rajesh weblog.
regards,
Ramesh

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

Starting Conditions for Purchase Order WF

Hi all,
We have developed a Workflow (Process-Controlled Workflow) for SRM Purchase Order. The requirement we have is that if the PO is released and then changed, only the WF should start again if the amount is changed. Any other field change in the PO should not trigger WF again.
There is customizing to define which fields should trigger WF for Shopping Cart, but I don´t found this for Purchase Order:
PRO--> SRM server --> sourcing--> Define Fields in Shopping Cart Which Trigger Workflow
Any suggestions?
Many thanks,
Ezequiel

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?
my idoc is PORDCR102 AND message type is PORDCR1. my requirement is this is EXIT should trigger before saving the data in me21n.
Edited by: rk.kolisetty on Jun 24, 2010 4:59 PM

Hi,
Following are the user exit relevant to T Code ME21n.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Rgd,
Chetan

Legal control for Purchase orders / Foreign trade requirements for MM

Similar Messages

Maybe you are looking for