on 11-05-2019 6:36 AM
Hello,
We use SAP B1 9.2
We use the "document flow? " model to follow up all the transactions of any client from A-Z.
I don't know how this model is called. It is shown in the following diagram:
-
||||||||||||||||||||||||||||||| ---------> Purchase Order -------------> GRPO ----> Purchase Invoice
|||||||| Sales Order |||||
||||||||||||||||||||||||||||||-------------------------------------------------> Delivery ----> Sales Invoice
In this model, each document (target document) is created from the preceding one (base document) by using Copy To or Copy From.
-------
Our starting document is the Sales Order. We put the BP Code (the client's code: say SHP1002: Queen Mary), and fill in all the stock items required by the client.
Then, we go through all the successive stages, up to Delivery. In all these stages, the client's code is still SHP1002.
--------
The crucial stage is Sales Invoicing. If we use SAP's menu, the Sales Invoice will be posted to SHP1002: Queen Mary.
But we don't want to do this for a number of reasons peculiar to our business.
We want to post the invoice to, say AGT1008: ABC Ltd, which is the paying agent.
--------
We have tried a number of solutions, but none is fully satisfactory:
Solution 1
We post the Sales Invoice to SHP1002 using SAP's Menu. Then by using Journal Entry (and a special add-on), we transfer the invoice from SHP1002 TO AGT1008. It works, but I feel there must be a better, faster, and more direct solution.
Solution 2
After we have created the Sales Invoice (from Delivery), we change the BP Code from SHP1002 to AGT1008. Then we post the document. But this method has ugly consequences:
(1) The link is broken. The Sales Invoice appears as a stand-alone document in Relationship Map.
(2) All the stock items listed on the Sales Invoice are issued a second time.
-----------
MY QUESTION?
Is there another alternative?
We are thinking of developing an SDK add-on which will work as follows:
We put a ComboBox on the A/R Invoice screen to select the BP Code we want to post the Sales Invoice.
We disable the SAP's native functionality, and use the functionality provided by the add-on instead.
The add-on will post the Sales Invoice to AGT1008, using the selected deliveries as base documents.
Hence, (I hope), the document links will not be broken, and the Relationship Map will show all the documents from A-Z.
Is this strategy feasible, and can it work as intended? Are there any considerations I should be aware of?
Any suggestions and comments most welcome!
Leon Lai
Hi Leon,
there is a standard feature called "Delivery Consolidation" available ( since long time ).
A good description I found here: Consolidating BPs
Basically you open BP Master Date for 'SHP1002', -> Accounting Tab -> Set Consolidating BP to 'AGT1008' and check 'Delivery Consolidation' -> Update.
Now Add an Invoice for 'AGT1008' and choose Copy From -> you will see open Deliveries from 'SHP1002' -> copy data -> add document -> relationship map is correct.
Let me know if it helped,
Maik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Kenan is giving you a wrong answer. Yes, you can change BP on AR Invoice but this change breaks all links to previous documents. This is how B1 works, there are no changes in 9.3 version.
The best solution would depend on your needs. Maybe you can try using UDF or different Ship-To address to separate deliveries to different BP?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Leon Lai Kan
I just tried it out in SAP B1 9.3, add a Sales Quation then copy it to Delivery and when it come to AR Inovice I can easly change the BP details, but you should take in consideration according to your settings the BP conditions, discount groups, and other features might differ from the one in the Sales Order,
I would encourge you to upgrade your SAP version to SAP B1 9.3, and if you need any help it's my pleasure to help you out with,
Regards. KENAN
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Maik
Thanks for your reply.
I think Payment Consolidation would be more appropriate for me.
In the past, it seemed there were problems if, AFTER the user has posted the Invoice to the Consolidating BP (AGT1008) , he changes, or deletes the Consolidating Partner in the client's Masterfile (SHP1002).
The invoice would not appear when doing an Incoming Payment on the AGT1008 Account.
----
However, it also seems that this "bug" has now been corrected by SAP.
So, now, even if the user subsequently modifies the Consolidation Partner in the Masterfile of SHP1002, this does not affect in any way the invoice already posted to AGT1008.
Now, I think I can use this SAP Feature to my company's advantage. Formerly I could not, because of the "bug".
Best Regards,
Leon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Kenan
Thanks for replying.
You mean it can be done in SAP (just by changing the BP Code at the invoicing stage?), without developing any SDK add-on?
This would be good news indeed for me! Almost too good to be true! In 9.2, it cannot be done (without breaking links)
Would you mind doing a test for me, because I don't have 9.3 yet?
---
Send me a snapshot of the Relationship Map of your existing scenario, i.e. Sales Quotation --> Delivery --> A/R Invoice.
I want to ensure that the links are not broken.
If the links are broken, I cannot use this method.
But if the links are not broken, it's a lifesaver!
------
Also, if you reopen your A/R Invoice screen, and click on base document on the menu, it should point to Delivery- confirming that the link is not broken, and that the A/R Invoice is not standalone!
Best Regards
Leon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.