on 02-01-2007 7:20 PM
Hi,
I get a lil' question for you all...
Do you know where you can find the link between the SRM BP number and SUS BP number?
Is there any FM or table that stores that relation between SRM and SUS?
for example in SRM the BP #3000032 means the BP #1000099 in SUS... Where can i find that relation??
Cheers,
Gerardo.
Points will be rewarded for useful answers...
Hello Gerardo R. Espino ,
Please see table BUT050 in SE16 transaction.
There must be some FM which will give you this details but your issues should be addressed by this table.
regards,nishant
please reward if it answer your query
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nishant,
Hi, thnx for your reply, but i checked the table and it seems to have the relationship between the partner and their contacts, like persons, employees, etc..
What i need is to find the numbers for same vendor in both systems, SRM and SUS...
Something like this: BP # 0003000352 in SRM is the BP # 0001000099 in SUS.
This is an XI message from SRM to SUS sending a PO:
- <SenderParty>
<InternalID schemeID="PartnerID" schemeAgencyID="BS_SRD_BACKEND">10000001</InternalID>
</SenderParty>
- <RecipientParty>
<InternalID schemeID="PartnerID" schemeAgencyID="BS_SRD_BACKEND">3000353</InternalID>
</RecipientParty>
There you can see both numbers BP in SRM and BP in SUS... Where can i find that couple...
Regards,
Gerardo.
Hi,
I have never worked on SUS so far but I can suggest you something which might help you.
Go to transaction BBP_PD
Give object Type as BUS2201 for PO
Object ID as PO number.
Do a execute.
double click on the line item which you got.
Look for the Partner:
here you will get partner functions.
What I feel that Requester in EBP(SRM) will fill send party and seller party will have value of vendor number.
Under partner function link,you will find requester as well as vendor number.
If you double click on the any line like partner -> Requester,you will get table name and other details for that.
Similary if you click on Vendor you will get details for that.
So ,I hope this will help you to analyse.
I feel that requester in your case will be filled with 10000001 and
vendor with 3000353.
regards,nishant
please award point if it helps.
Dear Gerardo ,
I hope that your following example is based on message PurchaseOrderRequest_Out.
<b>
- <SenderParty>
<InternalID schemeID="PartnerID" schemeAgencyID="BS_SRD_BACKEND">10000001</InternalID>
</SenderParty>
- <RecipientParty>
<InternalID schemeID="PartnerID" schemeAgencyID="BS_SRD_BACKEND">3000353</InternalID>
</RecipientParty></b>
BS_SRD_BACKEND is SLD defined in the XI system.
10000001 is BP for Company who is sending PO as sender.
3000353 is Vendor number in the EBP system.
Once PO reaches SUS , it reads VENMAP table to determine PARTNER_GUID and then it determines BP in SUS from BUT000 table for PARTNER_GUID.
Hope it clarifies your issue.
Thanks ....
Anand is pointed things in correct way.
There are some SAP FM which can be helpful to you
XML_DPO_TRANSFER ->Driver for Backend Connection via XML
There is a FM inside this FM
CALL FUNCTION 'BAPI_POEC_XML_INTERNAL_SEND' DESTINATION destination
Where it looks for details
po_header = po_header_b
po_header_cust = po_header_cust
vendor = vendor
sold_to_party = sold_to_party
ship_to_party = ship_to_party
bill_to_party = bill_to_party
ship_to_address = ship_to_address
So I will suggest you start with FM XML_DPO_TRANSFER and fill the input parameter and run in debugging mode to find the details.
Now you will ask me how to fill XML_DPO_TRANSFER input parameter I_HEADER.
Use the FM BBP_PD_PO_GETDETAIL and fill the I_OBJECT_ID with any PO number ,which u are looking at and do a execute for ,the internal table E_HEADER will be filled and copy this internal table data in above table and
try debugging & you will get fair idea how these struture in your XI is filled with data.
regards,nishant
please reward if it helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.