Delivery document number missing in SVT standard email triggered during Delivery Creation

[rohan_somji]

Hi Gurus,

In SVT, we have a functionality of Setup online checks which is used for online blocking of Sales / Delivery / Purchase / Production. If we have all the right configurations completed and if we have Specify Quantity Limits and reaction on overall status defined where lets say we have defined send message for information / warning and Error for regulations then we get a standard SVT email based on configuration completed in Setup online checks. The email scenario works absolutely fine for Sales / Purchase and Production. The document no is captured in email body for all the 3 scenarios. But this does not happen in Delivery. Here as soon as I create a delivery and hit save and since material is SVT relevant an email gets triggered. But in the delivery creation scenario the internally generated Delivery number is missing and it appears blank. During debugging I got to know that email gets triggered before internally generated delivery document no is generated and hence delivery document no appears blank.

I need to know if this is a standard issue or if there is something missing from my side. I have used all standard FM's for sales / delivery / purchase and process. But still delivery number appears blank. Note here once delivery number is generated and saved in LIKP table after delivery is saved, now when we make a change in delivery lets say we change the quantity and I save the delivery number, this time delivery document is available in email body as well.

There was a note from SAP 2077372 - SVT: Output of reference document number in messages for online check. Here they mentioned the same problem "You use substance volume tracking and, in particular, the online checks. You create a delivery from a sales order in the background, for example. You send the messages from the online check by e-mail. However, the system issues the value "$1" instead of the delivery number. You want the system to issue the number of the reference document (for example, the sales order) to facilitate further analysis. Reason and Prerequisites. There is a program error. The system performs the online check before saving the delivery. However, the delivery number does not exist at this point in time. The value "$1" is used as a placeholder."

But we are on upgraded version of ECC 7.0 and this patch is already updated in the standard FM's.

Kindly let me know if anyone has solution for the same. Thanks.

Regards,

Rohan

[christoph_bergemann · Accepted solution]

Dear Rohan

you have invested a lot of time (e.g. During debugging I got to know that email gets triggered before internally generated delivery document no is generated and hence delivery document no appears blank.).

If you have done the same check as for "sales" part and here  it works: I would assume that this is an error. But you should invest a little bit: Normally: if the delivery is not saved, you have no number. I would be really surprised (but if i look to your explanation...) that SVT will trigger something without "save"; I would suggest to start OSS dialog.

Small corrrection/hint: I assume you have instaled SAP ERP 2006 with EnhPack 7 (there is no version ECC 7.0 according to SAP definition). As the OSS number is part of your system the behaviour is strange.

IF you follow the ABAP code process (just do the same and debug): can you find the place at which the OSS is inserted? May be you can collect additional informaiton

C.B.

[rohan_somji · Accepted solution]

Hi Christoph,

Thank you for your reply. Firstly my bad for typo ECC 7.0. I was referring to ECC 6.0, EHP 7.

OSS note 2077372 is available in FM CBRC_CHK_ONLINE_GEN_MESSAGES. SAP has added one more FM CBRC_LIB_KEY_SPLIT in the correction code here. This FM updates the reference document no.

In case of Sales Order, the reference document number is nothing but the internally generated sales order number. So in the end when the email is generated document number and reference document both are same i.e. sales order number.

In case of Delivery, the reference document number gets updated as sales order no which is very strange. But in debugging we could see that code says pick value from VBAP or LIPS as reference document number (Line no 128 in the code) in FM CBRC_LIB_KEY_SPLIT. Since LIPS is empty VBAP value VBELN is picked up and this gets processed ahead. The email which gets generated has Sales Order as reference document number. But there is another field "document" which remains blank.

So in the end in delivery, document number is blank but reference document is sales order number.

And I have tested this in 3 different systems. Sandbox, Dev. and QA. I can see the same behavior in all the 3 systems.

Before I raise an OSS I just wanted to ensure that I hope this is not a functional issue because SAP will not support us then.

Please let me know. Thanks.

Regards,

Rohan

[christoph_bergemann · Accepted solution]

Dear Rohan

for safety reasons I write down your explanation and what I understood and then we will se..

for

In case of Sales Order, the reference document number is nothing but the internally generated sales order number. So in the end when the email is generated document number and reference document both are same i.e. sales order number.

This is feedback...

As we don't use the process and I did not checked code... A sales order has a number. Sales numbers are handled using VBAK. In a sales order you can have some "items" These are handled in VBAP.

In CBRC20 the "key"  to support the user is "sales-order + sales order item" in one cell. I would assume to get the same in eMail.

In this context it seems to be we have "two" fields; one called "Document" and the other "reference". For Sales order: it seems to be that you get "VBAK" number in both fields.. this seems to be logic as "Sales order document" is the "starting point" in SAP SD process.

for.

In case of Delivery, the reference document number gets updated as sales order no which is very strange. But in debugging we could see that code says pick value from VBAP or LIPS as reference document number (Line no 128 in the code) in FM CBRC_LIB_KEY_SPLIT. Since LIPS is empty VBAP value VBELN is picked up and this gets processed ahead. The email which gets generated has Sales Order as reference document number. But there is another field "document" which remains blank.

So in the end in delivery, document number is blank but reference document is sales order number.

This is feedback

In most cases: delivery is generated via Sales Order" manually (starting fomr Sales order you can direct generate delivery) other options exist as well, Internally. in SAP SD  a "document" reference is generated as. Delivery order X belongs to sales order (this is needed to look for document flow).

For: VBAP or LIPS as reference document number  => this is the "item" level (LIKP is the "header" table of delivery and LIPS is the "item level")

Now the "technical" part is coming up:

Since LIPS is empty VBAP value VBELN is picked up => this is a kind of "strange" (but can be in your special situation correct)

Simple example: You have a material number X in system.  Then you generate the Sales order using the material number X. Now you have populated "VBAP". Then you move on in generating the "Delivery".

The delivery "just" take in most of the cases data from "Sales order" and therefore at the end of process: LIKP must have value and LIPS must have value (in this case. material number X). Your debugging results shows: LIPS is empty: This can not be (in >80% of cases): But if so: May be SAP has decided, If, by whatever reasons;  we have delivery but no item use next appropriate value (VBELN) to populate data structure

I just "googled". VBELN seems to contain the "sales order" number (this is the "reference part")

PLease check therefore: can you find (using se16) the sales order number in VBAK, the item in VBAP,  the corresponding delivery in "LIKP" and if existent item in "LIPS"? If no item exists in LIPS: ask your self (and get in touch with SAP SD consulant) : why do we have no item

If LIPS contain value that behaviurs as explained by you is an "error". I would expect that document fields will get "LIkp/LIPS" information, and "reference field" will get VBAK/VBAP information.

Conclusion: after your explanation: please check your System. It seems to be that SAP has decided to support a "backup" scenario and therefore in the eMail you find the sales order number, but not delivery number

C.B.

[rohan_somji · Accepted solution]

Hi Christoph,

In Delivery, Reference document number to be the sales order number is fine. The code is written that way. Because even after delivery is created and lets say we make a change in quantity and save the delivery the reference document number is still the sales order number and document number is the Delivery number(Note: Now the delivery number is available as the delivery was saved and the current changes were done in the edit mode and not create).

But what do I do with the issue of blank delivery number in the create mode.

Below is the example of the first line in the email body generated during delivery creation. Here document number is blank and reference document number 0002215632 is the sales order number here.

Document: , item: 000010 (reference document: 0002215632-000010 ) (Error)

I need to know why is the document number is coming blank??

Regards,

Rohan

[christoph_bergemann · Accepted solution]

Dear Rohan

this is my current experience with "deliveries".

If i create a delivery in our systenm, number of delivery is availble after save, There is no need to look for "Edit" mode as you have to use it,

So if after create (VL01N) you don't have a number then may be "additional customer specific routines" are acting

regarding

"lets say we make a change in quantity and save the delivery the reference document number is still the sales order number and document number is the Delivery number(Note: Now the delivery number is available as the delivery was saved and the current changes were done in the edit mode and not create)."

if i read this part i would be satisfied. You have changed the delivery; the system sent an eMail

Email contains as "reference number" sales order (i could accept) and for document "Delivery number" (I could accept)

Both numbers are a good starting point to look for options (if you are experienced SD user).

Can you check with ABAper this:;

"

Document: , item: 000010 (reference document: 0002215632-000010 ) (Error)"

This is the text you have received. I am not 100% sure: is the "(Error) indicating that you hgave exceeded the threshhold level daramtically?

I would assume that in the FMs you have shown (or may be different one) the system tries to generate teh text as

Document & item & (reference document; & ??) etc. the "first" "&" should be used to store delivery number.

And here ist the "problem". There is no number detected; but strange thing is: item number is filled...

No idea why system is acting like this. Best could be to start OSS dialog (may be after some additonal checks)

C.B.

PS: coming back to OSS message you have shown

""prerequisites. There is a program error. The system performs the online check before saving the delivery. "

This issue still seems to be in place. The only difference is: now you get the "item" number in the document; but sill no delivery number=> if SAP hasn't move the code to "after the save" part you will not suceed

[rohan_somji · Accepted solution]

Hi Christoph,

Yes this is an appropriate scenario. The email gets triggered based on configuration of relative limits updated. Since the quantity has exceeded, SVT checks are getting triggered. There is nothing wrong with the process. It is just the email content for Delivery.

I have gone through the standard FM's triggered in the debugging mode and what we could see that before the final email is triggered, the content which is generated in the internal table does not have Delivery number updated.

But in case of Sales Order we see the internal table is updated with the sales order number before email gets triggered.

Regards,

Rohan

[rohan_somji · Accepted solution]

Hi Christoph,

Any suggestion or you think I need to raise an OSS for this??

Kindly let me know.  I will close the thread then.Thanks.

Regards,

Rohan

[christoph_bergemann · Accepted solution]

Dear Rohan

you should start OSS dialog as you are using (what I have seen her) the most current SAP version (including the OSS as discussed). I could imagine that community might be interested to get results here.

1.) did SAP accept OSS?

2.) and therefore deployed a correction? anf if so: with which new "OSS Note" number

C.B.

PS: it could be of interest to collect more information in context of this "eMail trigger approach". e.g. in Purchase scenario you can start with puchase requisition (and try to trigger eMail if needed); then move to purchase order (and you would may be again trigger eMail). Now it would be of interest if in Purchasing scenario we have "similar" issues to check (my expectation would be: in purchase requisition part. we will get this "document number" in the email; but not sure about purchase order part; will there be as well a "reference doucment" linked in eMail context... quite interesting topic).