Po replication to backend

Hi experts
I have I problem and I would like to know if someone had this problem and how it could be solved.
I am using SRM 5.0 in extendeed clasic scenario, for some reason some POs are created and imediatelly tranfered to backend even if no aproval occur, I have several POs in my backend and in SRM it is status AWAITING APROVAL..
Where is the problem in workflow or in the replication program?
Thanks
Nilson Fonseca

Hello,
Shopping carts might get stuck in status I1111 due to communication
problems with the r/3 backend. The system tries to resubmit the
carts with the given spool paramenter interval and if it is not
transferrred within that time, the shopping cart gets the status
I1111. This has nothing to do with the order or number of shopping
carts. Please check if you have maintained a SPOOL_MAX_RETRY >=10
in Customising ->Set Control Parameters.
As per note 441768 "Displaying canceled shopping carts in monitor", you
should schedule program BBP_ALERT_SB_NOTTRANSFERED. This will select
carts stuck in status I1111 Item in Transfer Process for more than 2
hours and send them to the Application Monitors to be resubmitted. You
can then logon as a user with the Administrator role and resubmit these
carts by choosing the "Transfer Item Again" button.
Please note that the following notes must be applied for this to work.
854478 Alert monitor: No longer possible to transfer shopping cart
865797 BBP_ALERT_SB_NOTTRANSFERED: Incorrect status set
Also In addition to the above suggestions, Kindly also apply the note
1022756.
I hope this information helps you to resolve this issue.
Kind regards,
Gaurav

Similar Messages

SRM 7 ECS : Prevent PO replication in Backend

Hi Gurus,
We are building SRM 7 with Extended classic.
I would like to know how to prevent some POs (thanks to some criteria we will put in customer fields) to be replicated into the backend (but which have to be sent to the supplier).
Many thanks in advance.
Regards.

Hello,
As you are in Extended Classic Scenario, if i am correct ( i don't have a SRM release in front of me) SRM PO replication to backend is triggred by function module BBP_PD_PO_TRANSFER.
This function module call should be triggered itself by a workflow event (maybe Setreleased as for SC transfer).
So, you could create an enhancement in this function module in order to not process its ABAP code (depending on you management rule).
Nevertheless, you will have to:
1- manage by your own means the PO header and item status,
2- check no row is populated in table BBP_DOCUMENT_TAB as SRM PO is not transferred to R/3 backend,
3- check report BBP_GET_STATUS_2 is executed normally (no dump due to those kind of PO),
4- (i am not sure) manage logical system linked to those PO.
Regards.
Laurent.

Set_types - Replication from Backend to SRM

Hi all SRM Gurus!
I have this specific problem:
Material Type FERT have been replicated to SRM. For the time of the replication the type didn't include the purchasing view, as it was not intended for purchase.
Now the business wants to make it possible to use the FERT type for purchasing, and therefore the purchasing view has been configured and added on the R3 side. But - when I replicate the product categories, I dont get the Set_type for purchasing in COMM_HIERARCHY. I can add it manually, but this is, from my perspective, not the right way to do it.
Can anyone help me?
Best Regards
Maria

Hi
As per my undesrtanding, Replicating Material Configuration data from R/3 does not seems to be a good approach at all.
You need to replicate only the Product hierachies (using tcode - COMM_HIEARACHY) in SRM.
Let me know your exact requirements behind this, why you taken this approach ?
What type of EBP scenario you are currently into ? Which SAP Version ?
Regards
- Atul

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

SRM PO replication to backend ECC (Extended Classic Scenario)

I would like to have inputs on this scenario, as which BADI we need to use and what we need to do exactly to replicate PO from SRM 5.5 to ECC 6.0.
Thanx and Regards

Hi,
just try out the following:
If you activate the BAdi, make sure to take over all Import params into your Export params!
Otherwise data may be lost!
Here is an example:
*-- data declaration
Data: wa_longext like line of ct_longtextt,
          wa_item like line of et_item,
          zw_index type sy-index,
          zw_counter type ec_counter.
*-- take over all import data to exp params
es_header = is_header.
et_item[] = it_item[].
et_partner[] = it_partner[].
et_account [] = it_account[].
et_orgdata[] = it_orgdata[].
*-- Change data
*-- modify given vendor longtexts (ITXT) for example with a standard text
*-- for all positions
clear zw_index.
Loop at ct_longtext into wa_longtext.
zw_index = zw_index + 1.
if wa_longtext-tdid eq 'ITXT' ." Vendor Text
wa_longtext-tdline = 'Here your Text'.
modify ct_longtext from wa_longtext index zw_index.
endif.
endloop.
*-- or if you would like to add a line of text to a position
*-- loop over positions and read text for vendor text
loop at et_item into wa_item.
clear zw_counter.
loop at ct_longtext into wa_longtext
where guid = wa_item-guid
and     tdid = 'ITXT'
and tdspras = '???'." -> your language (E= English, D= German...)
endloop.
*-- if position contains vendor texts already, you know the counter index
*-- add 1 to counter to get the "new" index for your new line
zw_counter = wa_longtext-counter + 1.
wa_longtext-guid = wa_item-guid. "to combine the text with the SC position
wa_longtext-tdid = 'ITXT'.
wa_longtext-tdspras = '??'.
wa_longtext-counter = zw_counter.
wa_longtext-tdline = 'Your Text'.
append wa_longtext to ct_longtext.
endloop.
This is just an example which I have coded right now.
Hopefully without any syntax errors.
Of course you have to adopt this coding to your requirements.
Best regards
Andreas

Material Replication from Backend: DNL_CUST_PROD0 is stuck in SMQ2

Hi Experts,
I am getting this error while running R3AS for DNL_CUST_PROD0 adapter and checking the SMQ2 is getting into SYSFAIL status. The detail error says "Incorrect parameter with CALL FUNCTION" for Function Module BAPI_CRM_SAVE
Even, adapter DNL_CUST_PROD1, is getting SYSFAIL error in SMQ1. The detail error is Filter criteria Invalid on function module CRS_FIRST_DOWNLOAD_TRIGGER
Please suggest
Thanks
Rakesh

Hi
Here is the possible solution. Ii was facing this issue however was able to do.
First goto SMOEAC and check wheather CRM is connected with correct site attribute or not.
Then check all the RFC connection.
delete all the existing queues and R3AM1
now goto R3ac3
refresh all the Load and try again i Hope it should work and also maintain
system landscape in technical basic setting in SRM GUI(SPRO)
Regards
saurabh

Problems in Contract Replication SRM

Hi Experts,
I need your help....i'm trying to make the contract replication from backend system by the program BBP_CONTRACT_INITIAL_UPLOAD.
But there is a message erro in coditions as down
''End of discount condition validity > end of price condition validity''
The replicate will work but all the contract cames in SRM with memorize status and i have to edit all the contracts...
if i change the date of condition in r/3 contract, i can make the replicate without problem. But this is not a correct solution.
there is a way to solve this?
I saw the notes in SAP but my Support Package is the last one (SAPKIBKT11)
Thanks all
gustavo

Hello Gustavo,
We are facing the same problem and are trying to figure out the solution from you inputs.You have suggested 2 options
1. BADI : BBP_CTR_BE_CREATE
But this BADI will be called when a contract is to be created in the backend and how will this BADI be helpful when we are replication/uploading contracts from backend R3 to SRM
2. Maintain same pricing conditions in both R3 and SRM: could you explain in details what you are trying to say.
Thanks
Raghu

GOA distributed to backend as Scheduling Agreement

Hi,
SRM 5.0 - ECS
We have a requirement to transfer the GOA created in SRM to backend as scheduling agreement.
GOA replication to backend as a contract is working fine, but i could not crack on the SA.
Any tips would be useful.
Regards
Sudhakar

Hi Sudhakar,
like said, you need to program within BADI to differentiate which document is created. By standard the system takes the first doc type and distributes it to the backend depending on the doc type. To make it more clear: the functionality to either create a Contract or a Scheduling Agreement does not work without programming. By customizing, only one document can be created.
Typcially there are specific doc types in Backend for Contracts and Scheduling Agreements by standard. So it makes sense to follow the standard and create different doc types for Contracts and Scheduling Agreements and use these doc types within the BADI to tell which document is supposed to be created.
Cheers,
Claudia

Regarding Syncbo types in MI

Hi,
Please let me know as the difference between Two way synchronization BO and Timed Two way synchronization BO.
When shud we go for S01 and when for T01 Sync BO
Regards
Raja Sekhar

Hi
2-way Executes both data download and upload in each access from a client to the server. The delta BO determination between the application DB in the backend system and the mobile client local DB is triggered in each access. This means it is based on the latest state of the backend system at the point of each access. However, the performance can be low, as it is synchronously performed.
Timed 2-way Executes both data download and upload in each access from a client to the server. Since the delta BO determination between the application DB in the backend system and the Replica DB for the device in Smart Synchronization is executed via periodical job, the performance is high. However, there might be cases where the Replica DB is not most up-to-date at the time of an access from the device.
Synchronization Type- Timed 2-Way (T01)
Downloader-Executed. Base data for delta detection is replication database.
Uploader- Executed if message contains upload data
Replication from Backend- Triggered by scheduled job
Synchronization Type- 2-Way (S01)
Downloader-Executed. Base data for delta detection is the backend system.
Uploader- Executed if message contains upload data
Replication from Backend-Triggered by the device
regards
Arun

Changes to Limit Orders in SRM do not replicate to ECC

Hello Gurus,
I am using SRM 7.02 Extended Classic with ECC 6.0. We are having issues when making changes to a Limit Purchase Order. Once the change is made and Ordered, the information does not update the ECC PO.
An additional output must be generated to update the backend system.
I have found some information on SRM 5 but not for 7.
Any help would be appreciated.
Best regards,
Mary

Hi,
I thyink the replication to backend happens by RFC FM. what you can do is take the GUID of PO and run BBP_PD_PO_TRANSFER_EXEC FM. before doing this put a BP in FM B46B_DPO_TRANSFER at code where FM BBP_PO_INBOUND is called. Here you will come to know what data exactly is getting passed to ECC.
thanks,
sankar.

Organisational units not in transaction BP

Hello Guru's,
We are on SRM 5.0 en we use HR Replication. Backend system is SAP ECC 6.0. So we are replicating the organisational units from the R3 system to SRM where it should create the org unit and the business partner in the organisational role. The organisational uinits recently replicated are visible in PPOMA but not visible in transaction BP. The business partner is also not created but it should be able to find the org unit when selecting Organisations in the field 'Find' in transaction BP ? So doe anyone know why these org. units are not visible in transaction BP ?
Thaks as ever!
Antoinette

this is correct , all the organization units will not come up as BP
you need not worry , if you check pposa_bbp , you will find an column which says BUsiness partner , only those will be shown in the transaction BP

ECC PO wtih reference to SRM PO

Hi ,
In my case PO has been crearted in SRM system, but PO has not been replicated in ECC system.
How do check for the reason why PO is not created in ECC system ?
Thanks and regards,
Amit R.

Hi
Which SRM and ECC versions are you using ?
Please implement BBP_CREATE_PO_BACK BADI or BBP_ECS_PO_OUT_BADI
FYI, In ECS, the PO will created in R/3 directly.
PO Replication to R/3
PO is "replicated" the same way with both scenarios. SRM triggers a RFC call in R/3 and BAPIS are activated (BBP_PO_CREATE and BBP_PO_SAVE*)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "Location" (R/3 plant you have replicated from your backend into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Do the setting in SPRO--> Cross Application Settings --> Define Backend System.
Where you need to select the Product category--> source system --> Purchase Group for the material and select in the drop down field " Always PR or Always PO". One you do the same it will work.
If you want a controlled extended classic scenario whereby once you create a Shopping cart it should create a P.R / P.O in the backend like classic scenario. You can use the BADI for this purpose which will overwrite the standard ECS settings for the particular product category / purchasing group / purchasing org.
Implement BADI : BBP_EXTLOCALPO_BADI
The following methods can be used : DETERMINE_EXTPO ,
DETERMINE_EXTPO_CREATE
Related links ->
SRM PO replication to backend ECC (Extended Classic Scenario)
PO's not replicated in R/3
Please let me know in case of any clarification.
Regards
- Atul

Error replicating materials from R/3 to SRM

I had to delete all materials from SRM master record to replicate agaim the materials object MATERIAL.
I have for my country one table CRMM_PR_TAX that contaim tax datas that comes with object MATERIAL during replication, after deletion I started the new replication and an error occurr:
Data cannot be maintained for set type CRMM_PR_TAX
Diagnosis
The data for a set can be maintained only if the product is assigned to a category to which the set type is assigned
Procedure
Check whether the product is assigned to a category that allows the set
Please someone knows can I chect it and configur agaim.
Thanks
Nilson

Hi
Please go through the links below ->
Note 1039863 - COD Performance : Problem with table CRMM_PR_TAX
Set_types - Replication from Backend to SRM
/people/marcin.gajewski/blog/2007/02/05/how-to-replicate-material-master-from-r3-to-srm
Set type 380BDF7B502D63F7E10000009B38FA0B does not exist
Note 381051 - Leasing: Category not found financing
Re: Mandatory set types
importnace of set type in comm_hierarchy transaction
Hope this will definitely help. Do let me know.
Regards
- Atul

BBP_ECS_PO_OUT_BADI

Hi all,
Does anyone know what this badi is used for?
Regards
Tony

Hi
Please go through the related links / pointers below ->
How PO data will be replicated to the backend system
Re: SRM PO replication to backend ECC (Extended Classic Scenario)
Re: Copy Local PO to backend
For Debugging from ECC into SRM
Re: Replication of PO to R/3
Re: Debugging from ECC into SRM
Other useful links ->
is there any BADI triggered when PO is replicated to backend??
New Plant - Replicate PO to backend
Re: BAPI to update PO's and Corresponding line items numbers **URGENT**
Hope this will help. Do let me know.
Regards
- Atul

What a basis person can do in MI7.1?

Hi!
We are going to have MI7.1 in shop.
Apart from install, upgrade, what else a basis person can do for some MI specific jobs
such as sync, replication and more?
Thanks!

Hi,
As per my knowledge is concerned BASIS person's work in MI is minimal as when compared to other components of Netweaver.
His job can include Insttall,upgrade/patching.
When it comes to Sync,replication from backend to middle your administrator should perform these tasks as he requires MI knowledge to do these tasks.
Administrator can also do the role based assginment etc.
Cheers,
Karthick

Po replication to backend

Similar Messages

Maybe you are looking for