on 2020 Jun 06 11:37 AM
Request clarification before answering.
Implement SAP NOTE: 2870267 - Central Finance: Corrections for SD Document Flow Enhancement (Source). with its prerequisite notes 2574028, 2662515 and 2615018 mention in the note
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We had the same issue and was able to fix it via sap note 2912060: Central Finance: Corrections for SD Document Flow Enhancement (Source)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
patrick.d nice finding (that the behavior in FPS1 is different). I wonder if this is changed in FPS2, but there are probably very few customers on this version that can answer this. Did you observe any differences in VBFA in both systems?
There is a chance that this is a bug, but, to be honest, I have not searched for correction notes.
If this is not a bug, but intentional change, I think that it might be possible to get the behavior that you show in your last screenshot by following the guidelines from note 2449464 - How to enhance the SD Document Flow (there is a *docx attachment in it with detailed explanation and sample code).
If I were you, before resorting to custom logic, I would search for notes using some of the terms mentioned in the attachment. The good thing is that you already have a working example in your internal system, so it should be possible to find out what is different in document flow treatment by debugging the includes mentioned in the enhancement guide.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is nothing wrong with your system.
The same behavior I see in an unmodified 1909 FPS1 environment.
I cannot give you all the details on the reason why this design decision was taken (probably only a SAP solution architect can give you a correct answer), but this is how TM documents are displayed via the document flow if you start from a SD document. It might have something to do with the fact that TM was originally used as a separate system and TM embedded is relatively new. It might happen that they introduce some improvement in a future release.
If you access document flow via the TM apps you can navigate to or open in a separate tab the documents that you see in the document flow:

All these links in column Business Document should lead to the corresponding application if your user has sufficient authorizations and if the apps are correctly configured.
My guess is that for document flow display starting from a SD document, the treatment of TM documents is similar to that of external transactions - you see the number, but you cannot navigate to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
the only changes I see documented are relatied to planning, not document flow:

but indeed, the customer system is on FPSP01 already and our internal one where i still see this line is not.

br
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Go to VA03, select that sale order and execute. Now from top menu bar, click on Environment > Changes where you can see what changes made to that sale order. In the above case, most probably, some deletion would have happened for the said line item
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1) Check VBFA table for this sales order number for correct doc.flow recording.
2) Check individual documents, not through this doc.flow, but using individual t.code (whether any line item is deleted or cancelled)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 12 | |
| 11 | |
| 8 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.