Maintain delivery condition in PO after PO output

[Former Member]

Hello experts,

Have searched a lot for below requirement but could not find the suitable reply.

Scenario: X dept user will create PO and take output. Later, Y dept user will maintain different delivery conditions in each PO line item before first GR.

Control Required: (1) Y Dept user should have authorisation of maintaining delivery conditions only and not for the other changes / additions in PO line

                           (2) PO should not require any amendment for delivery condition maintenance.

Is there any tcode / authorisation through which Y dept user should be able to maintain only delivery conditions.

thanks

[Prasoon]

Hi,

   If you want to restrict all the changes other than conditions tab, then you may follow the below steps:

1. Create a new field selection key in the path: OLME - Purchase Order - Define Screen Layout at Document Level. Here, copy AKTH and create new, say ZAKTH and make all the fields are display only.

2. Go to OMET transaction and create a new function authorization and assign the field selection key to the function authorization.

3. Go to user profile - parameter ID for the Y department users and assign the parameter ID: EFB with the value as the function authorization created in step 2 (01 in example).

    Now the user can maintain the fields in conditions tab only. Test the scenario and revert back.

    If you want to allow only delivery cost conditions and no other conditions like discount, surcharge / base price, there is no option in standard (except making all other conditions as automatic only) as of my knowledge. In this case, you may check the feasibility of development with BAdI: ME_PROCESS_PO_CUST

Regards,

AKPT

[Former Member]

Hi Prasoon,

Thanks for the information provided. Have tried this and giving below the test results.

1. User "Y" is able to maintain only delivery conditions - OK

2. But this change is subject to PO version management - This is not required, if delivery is being maintained.

3. "02" activity for PO document type was also demanded by the system - Can we avoid this by any chance.

Thanks in advance

[BijayKumarBarik]

Hi,

Check how version management designed for your purchase order . In your case you added delivery condition type by changing your PO with t.code: ME22N which in turn triggers next version number after PO changes. If this is specific procedure of procurement with standard design, then deactive version  management by deselecting check box for your PO document type  with purchase organization  with document category F.

I am not sure why different user groups involved for a purchase order creation process and based on purchase organization nature, purchasing group involved-in, can handle this purchase order creation process and add delivery cost. As version number in PO layout- you can find the PO layout in each case- if any reference required!

Regards,

Biju K

[Prasoon]

Hi,

   Version will be generated based on the version relevant field settings in the configuration. Refer the doc:http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0266bdb-d55d-2e10-d7aa-87a3294da...

Regards,

AKPT

[Former Member]

Hi Biju,

Thanks for the reply. This actually is a business requirement where delivery conditions (not know while creating PO) is to be maintained by other department user at a later stage.

thanks

[Former Member]

Thanks Prasoon,

Document is useful for PR version. But not showing information about PO fields path relevant for version. Could you please check accordingly.

thanks

[former_member233510]

Please check the section New Versions of External Purchasing Documents in the following link

Version Management - Purchasing (MM-PUR) - SAP Library

[former_member213836]

We can have version relevant field control for PR only & not for PO. For PO, not all fields will trigger new version. As mentioned above any updates to field Relevant for Printout of changes (Change notices), Document assignment and address will generate new versions in PO. Seems you have EKPO - EFFWR as print relevant field and hence new version is being created.

Regards,

Niranjan

[Former Member]

This option is not suitable as in some cases version trigger is required and in some case not. As a workaround, I tried IMG->Logistics execution->Transportation>Shipments option already available in standard SAP. But, could not configure the complete steps for the scenario as under:-

"Import PO is created maintaining required  Freight condition with ZERO value as the same to be handled through transportation module (path mentioned above) where VL01N, VT01N,VT02N,VI01, VL32N etc transaction comes into picture - have found these after few online search."

Could anyone please share the complete configuration / transaction steps for the above requirement

thanks

[Prasoon]

Hi,

   You need inbound delivery to process with Transportation Management. Refer the doc: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70fbd5dc-8f5f-2910-2085-c658dc145...

Regards,

AKPT

[Former Member]

Hi Prasoon,

Thanks for the reply. I had referred this document earlier (its very good for the kind of requirement given). Steps are OK in this document, till creation of Shipment document (VT01). But there is no clarity from Creation of Shipment cost (VI01) onwards as how the cost (freight for eg) is coming. May be steps are missing. Could you help.

Thanks

[Prasoon]

Hi,

   You can create the shipment cost document in VI01 transaction, with reference to the shipment document. The freight values can be pulled based on the condition records maintained (in TK11) or it can be inserted manually in the shipment document, based on the pricing procedure assigned.

   You can check the errors using the error log and you can go to the item details - and go to conditions tab where you can check the conditions triggered and the manual conditions, if required. Refer the screenshot from VI01:

Regards,

AKPT

[Former Member]

thanks, could your please share the steps to create / assign this pricing procedure through which we can maintain manual freight value. And how to maintain the same for all inbound delivery line items OR as header condition value for all inbound line items.

thanks

[Prasoon]

Hi,

   I would suggest to check the wiki doc: Transportation Configuration and Process Flow - ERP Operations - SCN Wiki  which explains the complete configuration and scenario. Check the same and revert back if you need further support.

   Also refer the doc:

Regards,

AKPT

[Former Member]

Hi Prasoon,

Thanks again. Both the links are very useful for outward freight (Dispath), but my requirement is for Inward freight (Purchase) where routes cannot be fixed as supplier can be from any location. Moreover, transaction code would be VL31N / VL32N (inward freight) in this case against VL01N/VL02N as is there for outward freight. Please see if any link is available for this requirement.

thanks

[Prasoon]

Hi,

   The concept is same for inbound as well as outbound shipment. Request you to follow the same process, and check the error log, correct the same and proceed!

Regards,

AKPT

[Former Member]

This message was moderated.