check if a document position has been distributed

[matteo_montalto]

Hello all @sdn forums,

a "simple" question: what's the best, effective way to determine, for PO and contracts, if a specific item position has been distributed/ordered correctly on the backend?

Additional info; we're working on an extended classic scenario, SRM 7. We used to check for status in CRM_JEST for what concerns distribution's info @ document granularity... But I guess there's a cleaner way to determine, given a position in a document, if it's has been distributed correctly or not.

Thanks for your help!

[former_member183819 · Accepted solution]

You need to educate the BUYER team if you are distributing the contract to backend system and every time BUYER make ensure that whatever contract has distributed to backend system after Approval. This process is a manual.

or BUYER physically has to check in the WEB front on Status Distributed and in ECC ME33K.

After approval of contract not reached means BUYER has to report to IT department for further investigation. However SAP given some logs to disply whyfailure distributing contracts.

but BUYER community wanted automatic ERROR message if the CONTRACT not reached backend system if they were not distributed.

Our onus to teach BUYER team on status of contract /Purchase order and if any thing abnormal BUYER team has to report to IT department .since STATUS are set wrong if some accidents happen or linkages are broken.

[matteo_montalto · Accepted solution]

Hi Muthuraman,

our question is related to a custom development we would like to implement.

It's quite simple; under certain conditions, we would like to close some fields of an item to prevent user modifications.

In the above stated "certain conditions", there's the desiderata of this thread: if a specific position of the contract/purchase order has been correctly distributed to the backend, then some fields should be closed for modification.

Question quite tricky as you can easily notice, checking for position distribution is more specific than checking a document distribution, as some items could be added to the document after a first, second... n distribution.

Thanks for your help

[former_member183819 · Accepted solution]

Sorry . Please rephrase your question and create another thread . i could not undertand the question fully .

[matteo_montalto · Accepted solution]

Hi Muthuraman,

I'd try to rephrase the desiderata here.

Our specification is to "lock" some fields at item level when the item itself has been successfully transferred to the backend.

This could be obtained by showing the desired fields as read-only in SRM 7 webdynpros.

Obviously, in order to evaluate if a field must be shown as read-only, we should be able to determine if the item has been correctly transferred.

This seems not so trivial because:

- we could check for document's status... but in our scenario, item positions could be added even after a successful distribution, so an overal check on the doc's status is not sufficient;

- at item level, we did not find any field in DB tables which can be relevant for determination of a successful distribution.

Hope the question is a bit clearer now.

Best regards,

M.

[former_member183819 · Accepted solution]

Learnt from below

Our specification is to "lock" some fields at item level when the item itself has been successfully transferred to the backend.

This could be obtained by showing the desired fields as read-only in SRM 7 webdynpros.

Obviously, in order to evaluate if a field must be shown as read-only, we should be able to determine if the item has been correctly transferred

-

---

Do you want to make some fields in the contract non editable ( Buyer should not allow to change) after the contract has been distributed to backend.

please give some practical example whick fields do you want to make non editable after the contract has reached to ECC.

Assume that now you made it as non-editable. Later you want to revise the contract , that time you must able to edit it. How you are going to manage to modify the contract

[matteo_montalto · Accepted solution]

>

> Do you want to make some fields in the contract non editable ( Buyer should not allow to change) after the contract has been distributed to backend.
> 
> please give some practical example whick fields do you want to make non editable after the contract has reached to ECC.
> 
> Assume that now you made it as non-editable. Later you want to revise the contract , that time you must able to edit it. How you are going to manage to modify the contract

Hello,

an example of (standard) field we would like to make non-editable: position's type (material, outline, service lines and so on).

After a successful distribution, the user should not be able to modify it (otherwise we experience problems on the R/3 /ECC side). This is not done by SAP standard, we should implement this via web dynpro enhancements.

Other fields, for example some custom ones, should be non-editable after distribution as per customer requirement.

In case of contract revision, some operations are allowed (e.g., adding new position manually or from shopping cart, changing price, quantity or description of an item...), others are not; in such (few) cases (which should be considered as procedural errors) a customer maintenance service will provide support.

[former_member183819 · Accepted solution]

>

> >

> > Do you want to make some fields in the contract non editable ( Buyer should not allow to change) after the contract has been distributed to backend.
> > 
> > please give some practical example whick fields do you want to make non editable after the contract has reached to ECC.
> > 
> > Assume that now you made it as non-editable. Later you want to revise the contract , that time you must able to edit it. How you are going to manage to modify the contract

>

> Hello,

> an example of (standard) field we would like to make non-editable: position's type (material, outline, service lines and so on).

> After a successful distribution, the user should not be able to modify it (otherwise we experience problems on the R/3 /ECC side). This is not done by SAP standard, we should implement this via web dynpro enhancements.

>

> Other fields, for example some custom ones, should be non-editable after distribution as per customer requirement.

>

> In case of contract revision, some operations are allowed (e.g., adding new position manually or from shopping cart, changing price, quantity or description of an item...), others are not; in such (few) cases (which should be considered as procedural errors) a customer maintenance service will provide support.

Hi

you can not edit the data once you have distributed to the backend -material, outline, service lines and so on

This is standard SAP.

Please precise which filed you want to hide .

for example

Material master - MM - 10002 material if i distribute to backend i can not edit the Material number .

You can only make it as flag Inactive so that this item will be locked in ECC.

However system allows to change UOM for material by mistake but you should not edit the UOM field and this changes never reach ECC system .

you need to iactivate the first line item and add another entry for material master and add new data.

[matteo_montalto · Accepted solution]

>

> Hi 
> 
> you can not edit the data once you have distributed to the backend -material, outline, service lines and so on
> 
> This is standard SAP.
> 
> Please precise which filed you want to hide .
> 
> for example 
> 
> Material master - MM - 10002 material if i distribute to backend i can not edit the Material number .
> 
> You can only make it as flag Inactive so that this item will be locked in ECC.
> 
> However system allows to change UOM for material by mistake but you should not edit the UOM field and this changes never reach ECC system .
> 
> you need to iactivate the first line item and add another entry for material master and add new data.

Ok, this is what we have in our SRM 7 system (and I guess it's quite standard as far as what concerns the argument):

- item type field is opened for modification even after the distribution, you're right.

BUT...

if the document has been distributed:

- the user can change the type of the position, e.g. from material to service;

- the system reacts filling the item position type with the previous value (e.g., material) but then accounting details on the position are lost (the buyer should re-insert them manually).

We didn't find a note about this problem, therefore we'd like to make the field non-editable.

Other fields we would like to make read-only are substancially custom ones (as per desiderata of the customer).

THanks again.

[former_member183819 · Accepted solution]

You dont worry. Please create OSS message under

SRM-EBBP-CON

Definetly you will get correction SAP note .

I dont have SRM 700 system to test..

I do remember in old GOA contract - we can not change the item type once we distributed ...it is totally uneditable field.

please update here SAP correction note here once you get it.. Good luck.

My gut feelings you must get a sap correction Note. if SAP says it is standard behavior, you can plan for little development

---

Note 1463493 - Product id field disabled at item level in contract

Symptom

Central Contract does not allow the product ID to be changed.

Requirements:

a) The Central contract shall allow the Product Id to be changed when contract has not been released once.

b) The product Id within a central contract shall not be changeable if the contract has 'In Negotiation' status.

c) The product ID within a central contract shall not be changeable when the item has conditions independent from the status.