on 03-13-2006 10:51 AM
Hello all,
EBP 5.0, R/3 4.7
I have address maintained in EBP via web and added it to user in ppoma_bbp as default.
In SC when user check details Ship-To Address is appropriate, but in backend in Purchase Requsition delivery address is from associated plant.
Looking in BBP_PD for item Ship-To Address tables:
CRMD_PARTNER - ADDR_NR right one,
BBP_PDBGP no entries,
BUT000 root organization address,
ADDR3_DATA empty.
Grateful
Gordan
Hello Gordan
By default, the delivery address is not transfered.
There is an consulting OSS note on this topic:
you have to change B470_REQUISITION_CREATE (or copy it and call it with driver BADI) to enable the use of table "requisition_addrdelivery":
create requistion on backend system
CALL FUNCTION 'BAPI_REQUISITION_CREATE'
DESTINATION destination
EXPORTING
skip_items_with_error = skip_items_with_error
IMPORTING
number = number
TABLES
requisition_items = requisition_items_exit
requisition_account_assignment = requisition_account_assignment
requisition_item_text = requisition_item_text
requisition_limits = requisition_limits
requisition_contract_limits = requisition_contract_limits
requisition_services = requisition_services_exit
requisition_srv_accass_values = requisition_srv_accass_values
return = return
requisition_services_text = requisition_services_text
requisition_addrdelivery = req_addrdelivery
EXCEPTIONS
communication_failure = 1 MESSAGE msg_text
system_failure = 2 MESSAGE msg_text
OTHERS = 3.
Rgds
Christophe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Cristophe,
what if I would like to create purchase order in the backend from the shopping cart?
I am still struggling with direct creation of PO from SC. My order is still incomplete and system is creating PR instead PO in the backend. Problem is that I do not have administrative rights in the backend, only in SRM, so it is hard to debug "...REQREQ...". I will ask to debug it on quiet date: :o(
TIA
Gordan
P.S. 10 points for you already :o))
Gordan,
SRM is creating PR or PO depending on:
- SRM customizing (ex: always external proc + PR if incomplete, PO if complete)
- the interpretation of SC data by R/3.
IF your SC is considered complete by SRM (but with a fixed vendor and not a preferred vendor) the system will check if it can create a PO in R/3.
For this, each item will request a META_INTERPRETE_DATA to R/3, asking if it can create a PO. If R/3 considers this data as incomplete, it will reply to create a PR.
Usual cases of R/3 PR creation instead of PO:
- prefered vendor in SRM (and not a fixed one)
- custom checks in user exits in R/3
- error messages in R/3 (ex: O6 334 In the case of a fixed vendor, please enter info record)
- ...
To debug without debuging into R/3, you can also try the following:
- use BADI DETERMINE_TARGET_OBJECT and force PO creation
- so the system will always try to create a PO
- R/3 won't create the PO (for the same reason as in META_INTERPRETE_DATA), and will raise an error in SRM
- finally you get the real error in application monitor (SC --> backend application errors)
Rgds
Christophe
Hi RD, Hi Disha,
I am a little bit disappointed: I though you could find OSS notes by yourselves.... :-(((
Look at following notes:
767461 Transfer of ship-to address to back-end system
760824 EBP R/3 - delivery addresses
576665 EBP R/3 - no generation of delivery address for each item
450425 Delivery Address creates individual R/3 address number
427906 Transfer of the delivery address to the backend system
Rgds
Christophe
Thanks for the notes (You deserve Gordan points)
I agreee normally I must be able to find notes myself but sometimes like this one no search info is coming back still having tried with different terms.
Coming to the notes I read them carefully.
And I have a confirmation question.
In Note 450425 they propose 2 solutions, and I am interested by first one.
We want to transmit address only if changed in SRM.
Can you confirm my thoughts?
To enable address transmission I need to apply note 767461 (remove * in B46C PO CREATE and BC REQUSITION CREATE as I have a 46c system)
In that case all address will be passed. To avoid that I made in BADI BBP_CREATE_REQ_BACK and BBP_CREATE_PO_BACK a test to detect a change in address.
If address different nothing to be done, I let the EBP address to be transmitted. If adrress same then the EPB address nr field must be emptied and address determination will take place in the backend.
Correct?
Have you already done something like?
Thanks
RD
RD,
this is correct, but if you don't send any address data to R/3, it will be determined from the plant, and won't correspond to user default address. So the first option of note 450425 is not the good one for you (except if plant address is user's default delivery address).
The goal is to "play" with address number.
Option 2 from 450425 proposes a solution based on a mapping table between EBP and R/3 address numbers.
If address mapped, then pass R/3 number and no new address created in R/3.
Else pass the data and R/3 will create a new address.
Note 576665 proposes another solution, with a R/3 logic, to create only one address for all items (if same address).
Rgds
Christophe
PS: please create a new thread for new question
Hi Christophe,
We are having this reqt for transfer of shipping address frm SRM to R/3.Particularly,we have created multiple Delivery addresses through "Edit Internal Address" option in the Web screen.
When i add these in PPOMA_BBP atributes,i get to see all these values in the Web screen for SC in the node "Ship-to-address/Performance location" while creating a SC.Now my reqt is that when i change this Ship-to-address,this changed address should be transferred to the backend.
We are running on SRM 4.0(Classic Scneario) with R/3 4.7 as backend.
After going through the notes mentioned in this post,as given in note 450425,we need to mainatin a customising table for mapping EBP addr no & R/3 addr nos.
The 2nd workaround mentioned in this note will applicable for our scenario.
Can anyone tell me how about this mapping table which we have to maintain,what fields are to be considered?
Also,considering our release of R/3,do i need to implement the note 427906?
Any help will be highly appreciated.
Regards,
Disha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.