Purchase order increase limitation for user

Hi Experts
How can increase the purchase order limitation for the perticular user
which transaction code have to be run to change the purchase limitation
Regards
Piroz

Hi
Thread closed, I got it
Thanks

Similar Messages

BAPI_GOODSMVT_CREATE giving error purchase order is locked by user

I am calling multiple times BAPI_GOODSMVT_CREATE for same Purchase order to post goods receipt.
first goods receipt created successfully but second one has given the error the Purchase order is lockecd by USER 'XXXX' .
i am calling 'BAPI_TRANSACTION_COMMIT after each BAPI BAPI_GOODSMVT_CREATE.
i tried with passing parameter WAIT = 'X' in 'BAPI_TRANSACTION_COMMIT. then also getting same error message.
please any one tell me the solution

Hi
1. Check all the call is handled the release function(JCO.releaseClient(client)) for each call.
2. And check in finally
finally {
     try {
     if (client != null) {
       JCO.removeClientPool(SID);
       JCO.releaseClient(client);
     if(client.isAlive()){
          client.disconnect();
       JCO.releaseClient(client);                    }
     } catch (JCO.Exception ex) { }
Kind Regards
Mukesh

Workflow: purchase order created approve defferent users

hi friends,
i am creaed purchase order throw workflow. under that based on release stategy released and cancelld working fine. but our client requirement is two defferent release codes is customising one release code <=1000 is approved (current user), and another release code is =>1000 is approved (another user). so please give me a valuable suggestions.
advance thanks you.
Regards,
Bikshu.

Hi,
Based on the release strategy for PO, you can set the agents in config. SPRO - Materials Management - Purchasing - Purchase Order - Release Procedure for Purchase Order - Define Release Procedures for PO's - Workflow.
Here, based on the release group and release code, you can set the approval agents. This method can be used if your approval agents are fixed and known. If it has to be calculated at runtime, then you have to use other methods and rules.
Ensure that you have made an entry of 1 in the Workflow column for the appropriate release group and release code under SPRO - Materials Management - Purchasing - Purchase Order - Release Procedure for Purchase Order - Define Release Procedures for PO's - Release code.
In you step in the workflow, leave the agents as blank when you adopt this method.
Cheers,
Satish
Edited by: Satish Kumar R on Oct 13, 2008 1:55 AM

How to create purchase order using VA01 for BAPI?

how to create purchase order using VA01 for BAPI?

Hi Arun,
Please check this link
Example Program for BAPI_PO_CREATE1
Re: BAPI_PO_CREATE1
Questions in BAPI_PO_CREATE1
Problem with BAPI_PO_CREATE1
*& Report BAPI_PO_CREATE *
REPORT bapi_po_create.
Input File Declaration
TYPES: BEGIN OF ty_input_file,
column1 TYPE char50,
column2 TYPE char50,
column3 TYPE char50,
column4 TYPE char50,
column5 TYPE char50,
column6 TYPE char50,
column7 TYPE char50,
column8 TYPE char50,
column9 TYPE char50,
column10 TYPE char50,
column11 TYPE char50,
column12 TYPE char50,
column13 TYPE char50,
column14 TYPE char50,
column15 TYPE char50,
column16 TYPE char50,
column17 TYPE char50,
column18 TYPE char50,
END OF ty_input_file.
DATA: i_input_file TYPE STANDARD TABLE OF ty_input_file,
wa_input_file TYPE ty_input_file.
CONSTANTS: c_path TYPE char20 VALUE 'C:\',
c_mask TYPE char9 VALUE ',.,..',
c_mode TYPE char1 VALUE 'O',
c_filetype TYPE char10 VALUE 'ASC',
c_x TYPE char01 VALUE 'X'.
PARAMETERS : p_fname LIKE rlgrap-filename.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
Browse Presentation Server
PERFORM f4_presentation_file.
START-OF-SELECTION..
Read presentation server file
PERFORM f1003_upload_file.
IF NOT i_input_file[] IS INITIAL.
PERFORM split_data.
ENDIF.
*& Form f4_presentation_file
*& F4 Help for presentation server
FORM f4_presentation_file .
CALL FUNCTION 'WS_FILENAME_GET'
EXPORTING
def_path = c_path
mask = c_mask
mode = c_mode
title = text-001
IMPORTING
filename = p_fname
EXCEPTIONS
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
OTHERS = 5.
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " f4_presentation_file
*& Form f1003_upload_file
*& Upload File
FORM f1003_upload_file .
DATA: lcl_filename TYPE string.
lcl_filename = p_fname.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = lcl_filename
filetype = c_filetype
has_field_separator = c_x
TABLES
data_tab = i_input_file
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
EXIT.
ENDIF.
ENDFORM. " f1003_upload_file
*& Form split_data
Collect data for creating Purchase Order
FORM split_data .
DATA: i_poitem TYPE STANDARD TABLE OF bapimepoitem,
i_poitemx TYPE STANDARD TABLE OF bapimepoitemx,
i_poitem_sch TYPE STANDARD TABLE OF bapimeposchedule,
i_poitem_schx TYPE STANDARD TABLE OF bapimeposchedulx,
i_acct_*** TYPE STANDARD TABLE OF bapimepoaccount,
i_acct_assx TYPE STANDARD TABLE OF bapimepoaccountx,
i_services TYPE STANDARD TABLE OF bapiesllc ,
i_srvacc TYPE STANDARD TABLE OF bapiesklc,
i_return TYPE STANDARD TABLE OF bapiret2,
wa_header TYPE bapimepoheader,
wa_headerx TYPE bapimepoheaderx,
wa_poitem TYPE bapimepoitem,
wa_poitemx TYPE bapimepoitemx,
wa_poitem_sch TYPE bapimeposchedule,
wa_poitem_schx TYPE bapimeposchedulx,
wa_acct_*** TYPE bapimepoaccount,
wa_acct_assx TYPE bapimepoaccountx,
wa_services TYPE bapiesllc,
wa_srvacc TYPE bapiesklc,
wa_return TYPE bapiret2,
ws_po TYPE bapimepoheader-po_number.
break gbpra8.
wa_services-pckg_no = 10.
wa_services-line_no = 1.
wa_services-outl_no = '0'.
wa_services-outl_ind = c_x.
wa_services-subpckg_no = 20.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = 10.
wa_srvacc-line_no = 1.
wa_srvacc-serno_line = 01.
wa_srvacc-serial_no = 01.
wa_srvacc-percentage = 100.
APPEND wa_srvacc TO i_srvacc.
LOOP AT i_input_file INTO wa_input_file.
IF wa_input_file-column2 EQ 'HD'.
wa_header-doc_type = wa_input_file-column3.
wa_header-creat_date = sy-datum.
wa_header-created_by = sy-uname.
wa_header-vendor = wa_input_file-column4.
PERFORM conversion_output USING wa_header-vendor
CHANGING wa_header-vendor.
wa_header-comp_code = 'DE03'.
wa_header-purch_org = 'DE03'.
wa_header-pur_group = 'DE1'.
wa_header-vper_start = wa_input_file-column9.
wa_header-vper_end = wa_input_file-column10.
wa_headerx-comp_code = c_x.
wa_headerx-doc_type = c_x.
wa_headerx-creat_date = c_x.
wa_headerx-created_by = c_x.
wa_headerx-vendor = c_x.
wa_headerx-purch_org = c_x.
wa_headerx-pur_group = c_x.
wa_headerx-vper_start = c_x.
wa_headerx-vper_end = c_x.
ENDIF.
IF wa_input_file-column2 EQ 'IT'.
wa_poitem-po_item = wa_input_file-column3.
wa_poitem-short_text = wa_input_file-column6.
wa_poitem-plant = wa_input_file-column8.
wa_poitem-quantity = '1'.
wa_poitem-tax_code = 'V0'.
wa_poitem-item_cat = 'D'.
wa_poitem-acctasscat = 'K'.
wa_poitem-matl_group = wa_input_file-column7.
wa_poitem-pckg_no = '10'.
APPEND wa_poitem TO i_poitem .
wa_poitemx-po_item = wa_input_file-column3.
wa_poitemx-po_itemx = c_x.
wa_poitemx-short_text = c_x.
wa_poitemx-plant = c_x.
wa_poitemx-quantity = c_x.
wa_poitemx-tax_code = c_x.
wa_poitemx-item_cat = c_x.
wa_poitemx-acctasscat = c_x.
wa_poitemx-matl_group = c_x.
wa_poitemx-pckg_no = c_x.
APPEND wa_poitemx TO i_poitemx.
wa_poitem_sch-po_item = wa_input_file-column3.
wa_poitem_sch-delivery_date = sy-datum.
APPEND wa_poitem_sch TO i_poitem_sch.
wa_poitem_schx-po_item = wa_input_file-column3.
wa_poitem_schx-po_itemx = c_x.
wa_poitem_schx-delivery_date = c_x.
APPEND wa_poitem_schx TO i_poitem_schx.
wa_acct_***-po_item = 10.
wa_acct_***-serial_no = 01.
wa_acct_***-gl_account = '0006360100'.
wa_acct_***-co_area = '1000'.
wa_acct_***-costcenter = 'KC010000'.
APPEND wa_acct_*** TO i_acct_***.
wa_acct_***-po_item = 10.
wa_acct_***-serial_no = 02.
wa_acct_***-gl_account = '0006360100'.
wa_acct_***-co_area = '1000'.
wa_acct_***-costcenter = 'KC010000'.
APPEND wa_acct_*** TO i_acct_***.
wa_acct_assx-po_item = 10.
wa_acct_assx-serial_no = 01.
wa_acct_assx-po_itemx = c_x.
wa_acct_assx-serial_nox = c_x.
wa_acct_assx-gl_account = c_x.
wa_acct_assx-co_area = c_x.
wa_acct_assx-costcenter = c_x.
APPEND wa_acct_assx TO i_acct_assx.
wa_acct_assx-po_item = 10.
wa_acct_assx-serial_no = 02.
wa_acct_assx-po_itemx = c_x.
wa_acct_assx-serial_nox = c_x.
wa_acct_assx-gl_account = c_x.
wa_acct_assx-co_area = c_x.
wa_acct_assx-costcenter = c_x.
APPEND wa_acct_assx TO i_acct_assx.
wa_services-pckg_no = 20.
wa_services-line_no = 2.
wa_services-service = wa_input_file-column9.
wa_services-quantity = '100'.
wa_services-gr_price = '100'.
wa_services-userf1_txt = wa_input_file-column13.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = 20.
wa_srvacc-line_no = 1.
wa_srvacc-serno_line = 02.
wa_srvacc-serial_no = 02.
wa_srvacc-percentage = 100.
APPEND wa_srvacc TO i_srvacc.
ENDIF.
ENDLOOP.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = wa_header
poheaderx = wa_headerx
POADDRVENDOR =
TESTRUN =
MEMORY_UNCOMPLETE =
MEMORY_COMPLETE =
POEXPIMPHEADER =
POEXPIMPHEADERX =
VERSIONS =
NO_MESSAGING =
NO_MESSAGE_REQ =
NO_AUTHORITY =
NO_PRICE_FROM_PO =
IMPORTING
exppurchaseorder = ws_po
EXPHEADER =
EXPPOEXPIMPHEADER =
TABLES
return = i_return
poitem = i_poitem
poitemx = i_poitemx
POADDRDELIVERY =
poschedule = i_poitem_sch
poschedulex = i_poitem_schx
poaccount = i_acct_***
POACCOUNTPROFITSEGMENT =
poaccountx = i_acct_assx
POCONDHEADER =
POCONDHEADERX =
POCOND =
POCONDX =
POLIMITS =
POCONTRACTLIMITS =
poservices = i_services
posrvaccessvalues = i_srvacc
POSERVICESTEXT =
EXTENSIONIN =
EXTENSIONOUT =
POEXPIMPITEM =
POEXPIMPITEMX =
POTEXTHEADER =
POTEXTITEM =
ALLVERSIONS =
POPARTNER =
break gbpra8.
LOOP AT i_return INTO wa_return.
ENDLOOP.
ENDFORM. " split_data
*& Form conversion_output
Conversion exit input
FORM conversion_output USING p_ip
CHANGING p_op.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = p_ip
IMPORTING
output = p_op.
ENDFORM. " conversion_output
Best regards,
raam

Raise purchase order in me21n for 100 goods

HI,
i have problem. i raise purchase order in me21n for 100 goods.for that purchase order in MIGO i received 75 goods.when the invoice verification i found only 50 goods.how to clear in gr/ir in the month end process. please someone help me.
regards
subbarao

Hi
Reverse the MIRO and MIGO documents , and Post the MIGO and MIRO with actual quantity received
Regards
Rams

Discount limits for users

Hello,
I have a requirement which states that the status of a quotation in SAP CRM should change to 'X' when the discount on a line itemcrosses a certain limit. This limit would be specific to the user creating/editing the quotation. i.e. I need to configure discount limits for users and want the quotation status to be set based on whether the discount offered is within the limit of the current user. Please provide your inputs.
Regards,
Aditya Mishra

I would searck for appropriate badi that is triggered, when discount is set (check if badi CRM_PRICING_I_BADI is triggered at that moment).
Then you can use function CRM_STATUS_CHANGE_EXTERN to set appropriate status when conditions are met.
And of course you will have to put somewhere the info what discount limit is allowed for users. You can create Z table in which maintaine that data or use some user parameters...
Regards.

Purchase Order Histroy Limitation

We have the business requirement to process selective SAP purchase orders which grow in size to over 500,000 line items due to the PO history. However, the size of the PO has become problamatic regarding the amount of time it takes to run on our server. Our basis team has informed us the threshold for the PO history is approximately 30,000 line items. The scenario for this large POs is most prevalent for our CATS process where a batch job creates Service Entry heets from time keeping entries. A specific time sheet per contingent worker is processed at least 10 lines per week as orkers are asked to split time between lunch. The contingent worker charges time against 4-5 work orders in a given eek, which in addition to splitting time can be 25 line items per week per user. So this translates to 25 line items on the SES and 25 line items on an ERS Invoice. The current SAP limitation is forcing us to shorten the PO duration to 2 months instead of the anticipated 1 year life cycle. Also the processing time for approving the SES and processing the invoice takes approximately 24 hours because of the PO history. We need a resolution to at least make the PO last for a year, and would very much appreciate any insights on if anyone runs a similar process without encourtering our stated issues.

Hi there,
Please kindly consider the notes I attached to your message.
In general, aggregating part of the purchase order history documents
should be used here. Or you should close the purchase order and create
a new one. Surely we have technical restrictions and can not just
support the processing of such huge data volume.
As far as I can tell from here, using the aggregation transaction ME87
is the only possibility to consolidate this issue, i.e., reduce the
amount of data retrieved by the system to an acceptable amount. So
please let me ask you to aggregate some of your EKBE data for the
referring PO.
311089 Performance problems because of long PO history
694091 Further processing of aggregated documents
1.Regarding mass execution of PO's.
In this case you enter you selection data as it is on the start scree
of TA ME87, then you call in the menu program -> execute in backgroun
Then the aggregation will be carried out as a background job and
everything possible will be aggregated as you expected.
2.Details of aggregation can be checked in below notes
417933   Consulting note on purchase order history records ME87
This says that The aggregated records are saved in table EKBEH.
Also, since this will improve performance but if you need more you should follow the below advice.
Please create an index using the data in this note. Issue still is that
EKBE is very large.
1386608 MRN0: Performance problems for selection with receipt prices
For a detailed description on how to create an index,
please refer to the online documentation, 'Basis Components ->
ABAP Workbench -> BC - ABAP Dictionary -> Tables -> Indexes'.
Hope this helps.
Regards,
Matthew

Purchase orders and requisitions - R12 user interfaces

Hi,
I see that the purchase order can be registered in the system by two different interfaces (I'm running R12.1.1): Using Oracle forms (Navigation path: Purchasing Super user: -> Purchase orders -> Purchase orders) and using Java html pages (Navigation path: Purchasing Super user: ->Buyer workspace ->Orders).
I have two questions:
1. The second option (using java pages) is not documented in the usersguide. Is it fully in production or they are still developing it? Why there are two different interfaces for the same purpose?
2. I see that from Java pages interface I can only see requisitions, but I cannot enter new ones (Navigation path: Purchasing Super user: ->Buyer workspace ->Requisitions). Should I enable somewhere this or the requisition is not developed using Java pages interface?
Thank you

993322 wrote:
Hi,
I see that the purchase order can be registered in the system by two different interfaces (I'm running R12.1.1): Using Oracle forms (Navigation path: Purchasing Super user: -> Purchase orders -> Purchase orders) and using Java html pages (Navigation path: Purchasing Super user: ->Buyer workspace ->Orders).
I have two questions:
1. The second option (using java pages) is not documented in the usersguide. Is it fully in production or they are still developing it? Why there are two different interfaces for the same purpose?
2. I see that from Java pages interface I can only see requisitions, but I cannot enter new ones (Navigation path: Purchasing Super user: ->Buyer workspace ->Requisitions). Should I enable somewhere this or the requisition is not developed using Java pages interface?
Thank you
http://docs.oracle.com/cd/E18727_01/doc.121/e13410/T446883T443956.htm
http://www.apps2fusion.com/training_demo/puneetk/Professional-Buyer-Work-Center.pdf
HTH
Mahendra

Purchase order not visble for confirmation in SRM 7.0 portal

Hi all,
I am basically a portal consultant .The functional consultant configured in such a way that once the user creates a shopping cart it will create a Purchase order.
But when i go into central confirmation role and click on create confirmation document and search for the Purcahse order it is not getting displayed.
But There are some 11 pos in the system with 9 pos of status order and 2 pos status saved.
Please help me in resolving this.
Thanks and regards,
Rajesh
Edited by: Rajesh A on Jul 2, 2009 2:24 PM

Hope you might have some option called Express confirmation. check it up.
You can use this business process to confirm the receipt of goods. In SAP SRM, purchasers can create confirmations themselves, even if the purchase order is in the back-end system. It is possible to create express confirmations directly in the Check Status application without having to switch to another application.
Alternatively, an internal dispatcher or shipping department can take delivery of goods and confirm centrally. In this case, an additional approval workflow through the supplier is possible. Then, the goods receipt is posted in the back-end system.
You can also cancel an existing confirmation at item level. In addition to all of this, you can return partial quantities of individual items (or of all items) to your suppliers, and state the reasons for these return deliveries. These reasons are also transferred to the back-end system
br
muthu

Unable to view purchase orders in SNC for the supplier

Hi folks,
iam facing the problem of unable to view purchase orders in the supplier portal for my supplier.
ECC 6.0, PI 7.0, SCM 5.0 are the systems being used.
scenario is like :
for plant 1000, purchase order is created on vendor 1100 and idoc sent to PI successfully
also in PI in the integration builder i find messages saying successfully sent to SCM system
SLG1 transaction in SCM says message received successfully, (in the log i can see the plant, supplier, order no and order details)
when i try to login to supplier view with supplier login, iam unable to view the orders,
please let me know if iam missing any thing in this regard.
cheers.

Hi Kiran
Could you check queues
smq1 and smq2 ????
Does your xml posted successfully in SNC(SXI_MONITOR)... Can you open the payload document
inbound message-payloads-maindocument
Check thoroughly whether any error information ????
Check whether commit of xml is proper, or else refresh PI cache
For your internet user and the xml rfc user(user who is pushing the data into SNC), check whether any update errors are available in so01(inbox)
It could be a temporary problem, deactivate activate your supplier service in SICF. Could be problem with binding issue
Just to make sure data is sitting in SNC
Check this table
/1OM/ORDR7MP3100
Give your po number in field order no
If you find, then it is problem with binding...If you dont find, then the xml update process has issue
Kindly let us know the results
Best Regards
Vinod
Best Regards
Vinod

Purchase Order - No details for medium PRN in master record

Hi together,
we implement SRM 7.0 with Netweaver Portal 7.0. I'd like to create a purchase order with a user who has the role /SAPSRM/OP_Purchaser and is assigned to purchase organisation and purchasing group in the organizational structure.
If I create a purchase order and press "CHECK" I get the following error message: "Output: No details for medium PRN in master record" and I can't create the purchase order, only SAVE.
The user has the attribute PRI in the organizational structure and it is set in the user master data Defaults->OutputDevise locl.
Is there somthing more I have to do ?
Regards

I found the entries for output-printer in the PO.

Change MOT in purchase order using CIF Inbound user exit

Hello APO Experts,
Objective is to change start date of purchase order ( date at source location) in APO based on some date in R3.
Planning to bring R3 date using CIF Outboud user exit( CIFPUR01) in R3 and then further requirement is to a) calculate lead time in inbound user exit ( APOCF006) of purchase order in APO b) compare it with lead time of all available Means of Transport in that particular TLane and select one MOT say XX which matches that lead time c) Next part is to change existing MOT in the Purchase order and replace it with the new XX MOT.
For part c....I am wondering how can we change existing MOT in purchase order and replace it with a new one.Can it be achieved by the user exit APOCF006 in APO or something else is required.
Will appreciate your quick reply on this issue.
Thanks
Best Regards

Hi Nilesh
We have a similar requirement. I know its way long for you to remember but i would appreciate if you could share what did you do to achieve this.
Thanks
Abhishek Rai

Purchase order output determination thru User exit

Hi,
We are trying to find a way to determine the output for PO while creation (me21n) or modification (me22n).
We do not want to maintain output condition records for each fax/print/email etc..cases.
Can we do below thru a user exit or any other method ?
While creating PO, an OA partner will be chosen, so instead of maintaining the output condition records,
- user exit can access to OA's vendor master record and read Standard Comm.Method in Address section.
- according to comm.method, the PO message should be determined..
i.e: if comm.method is Fax, then message should be sent to OA thru Fax.
can this be done thru an exit ?
Thanks and Regards,
Ocal

Hi Stefan,
The steps are as follows:
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Reward me if it helpful
ASHOK

Purchase Order Release Strategies for Changed Amount

Hi Gurus,
We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
Example: Configuration is PO total amount <$5K requires only L1 approval. PO total amount >$5K requires L1 and L2 approval. PO was created for $8K and was release using L1 and L2 approvals. Receipts were posted to PO in the amount of $7K. Now the buyer has added an additional line item for $1K. The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item). Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
Has anyone done this before? Any ideas??
Thanks,
Gabe

from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1
USRC2
USRN1
USRN2
In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

Purchase Order Document limit to user

Hi All,
            My requirement is to limit a user such that user should not raise any purchase orders whose document total exceeding Rs. 5000.
             I need a functionality without using Approval procedures.
Thankyou.

To prevent entering PO for more the 5000 for specific users (in the code with id=2,3) you can use this code in SBO_SP_TransactionNotification stored procedure:
IF @transaction_type IN ('A','U') AND @object_type = '22'
BEGIN
if exists (Select DocTotal from [dbo].[OPOR] T0 where T0.DocTotal > 5000
AND T0.Usersign in (2,3)
AND T0.DocEntry=@list_of_cols_val_tab_del)
begin
     SELECT @error = 1, @error_message = 'You should not make more then 5000 !'
end
END

Purchase order increase limitation for user

Similar Messages

Maybe you are looking for