Peculiar case of GR posting

Question

HI I have tried posting the same problem but no one could answer, may be because I was not clear in asking my question ....this is the question and best possible way to ask  it...
We have a particular requirement for a type of subcontracting process (not the standard SAP subcontracting) as mentioned below. We create a Purchase Order for a material (without a standard cost). The Net price mentioned in the PO is the processing charges for the vendor (service charges). It does not indicate price for the material. When we receive the finished material from the vendor, we perform a Goods receipt. The stock gets updated and accounting documents are created.
Our requirement is to stop this quantity updating during Goods Receipt. But, at the same time, we would like the accounting documents to be created as we need to pay the vendor.
Is there any way of achieving this?
I understand that in the standard process, the parent item info record takes care of the processing charges. But this is process that has been customized differently as the client has SAP as well as legacy systems talking to each other. Turning off the qty updating at the material type level will turn it off for all purchase orders created for the material at that particular plant which is something we would like to avoid.
We would basically like to turn it off for particular purchase order type. The reason for turning it off is that after the GR is done, there is a separate process that comes from the legacy system and updates the same quantity of finished product and also posts the consumption of components. So, our basic requirement is , is it possible to turn off qty updating for the GR of a particular purchase order document type and yet create accounting document. Material is not a valuated material and has a standard cost zero.
These cannot be done:
Creating an account assignment PO will serve the purpose only for a material with value updating active and standard price is non-zero.
Flagging the GR non-valuated in the material data of the PO will also non-valuate the GR, i.e. no accounting documents will be created for the transaction. But it will not stop the quantity updating.
I was trying to think in terms of a new movement type which can carry out the required transactions. Any help in this direction or anything else that could solve the problem would be great!
Thank you MM Gurus,
srix..

Answer 1

Srix,
   There are so many factors which affect the way SAP is implemented in different clients. Some design decisions can be controlled and others not. Anyways, that is an altogether different beast and lets not get into that any further!
    Regarding your specific situation, it is rather difficult to give any clear cut recommendation without knowing all the details (although you have explained it fairly well) or in general via a forum. I will just add to what I mentioned earlier -
- Your requirement is to bring in only the value but not the quantity when you do a  GR. Obviously, standard SAP will not allow you to do this. Why? Simply because it violates standard accounting/auditing rules....How can you account for this value if you want it to reflect in your inventory (stock accounts) without any stock?
- The other way would be to non-inventorize the product and collect the value into a consumption account (account assigned PO - you can use a temporary cost object/GL account initially) and then let finance decide at a later time how they will allocate the collected costs.
- The other point I would emphasize (in general about implementing SAP) is that you are bound to run into such problems when you try to break the links within a truly integrated ERP system like SAP (separate stock update process like yours, backend MRP system etc). There are different reasons for having a multiple of legacy systems along with SAP in a company but if the reasons are not justified (better functionality, significant change management ect), then you will likely run into problems and increase costs (more interfaces, interface maintenance etc) over the longer run.
Hope this helps.
H Narayan