|
No GR and GI Posting After
TECO
How can we avoid the GR/ GI/ confirmation after the TECO or Order
settlement?
After TECO, you can still post the GI or GR and Confirmations on the
Orders.
This is a Standard feature of SAP.
To counter this, you can handle this with the following:
Create the user status and assign to the order type. In that you can
create the user status TECO and forbid the CNF status. So if you activate
your user status TECO to your order it will stop the confirmation.
or
You can control this using transaction BS22,
Select status I0045 TECO Technically completed, double click on this
value and then select the radio button for
RMPH Partially confirm order
RMPO Partially confirm operation
RMRP Incoming invoice
RMRU Confirm order
RMWA Goods Movement
RMWF Goods receipt for prodn. order
RMWI Inventory difference
RMWL Goods issue delivery
SDGI Post goods issue
and select Forbidden to Disallow the above functions, save it.
With this you can restrict GI/GR/Conf. for the Orders.
But these settings are at Client level, so please be careful.
or
Check with this user exit, CONFPP01.
This will help you to meet the requirement, with the help of your ABAP
consultant you can achieve this by activating this user Exit.
The system will throw an error message if you try to confirm an order
which has the TECO status.
Get help for your SAP PP Problems
SAP PP Forum - Do you have
a SAP PP Question?
SAP Production Planning Books
SAP
PP Certification, Interview Questions and Configuration Books
SAP PP Tips
SAP PP Tips and Production Planning/Control
Discussion Forum
Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
All product names are trademarks of their respective
companies. The site www.erpgreat.com is in no way affiliated with
SAP AG.
Every effort is made to ensure the content integrity.
Information used on this site is at your own risk.
The content on this site may not be reproduced
or redistributed without the express written permission of
www.erpgreat.com or the content authors.
|