PO is not populated to backend system

Hi,
We use Extended Classic Scenario and create a PO from sourcing cockpit.
When we create a PO we get a successful message. PO is created in SRM but is not populated to R/3.
In RZ20 monitor I don't have any message.
Regards,
Pierre

Hi,
If this error is in development/quality system and only with this one PO ?
If yes, then try to create a new PO and look if it shows in R/3.
Next thing, in transaction BBP_PD look for your PO and check for any errors and status of PO.
Regards,
Marcin

Similar Messages

SRM 7.0 Contract not replicating to backend system

Hi,
We have created CCTR global outline agreement in SRM 7.0 extended classic scenario. the contract is not replicating into backend. we have maintained necessary message types BLAORD, COND_A in ECC system as inbound parameters for partner type as SRM system.
when i looked rz20, i am seeing the message as "back end data could not be read"
When I executed function module B46B_CTR_TRANSFER I am getting an error, RFC destination could not be found.
please let me know what we are missing.
thanks
vem

"Hi,
I guess your SRM70 connected to backend ECC with EHP4 pack applied. If so, Central contract will not use IDocs instead it works on new eSOA technology where Xi/PI need to be set up to process service calls.
If you are not using EHp 4 pack on your ECC, then SRM70 use IDocs to distribute contracts to backend.
Thanks,
Jagadish
Hi jagdish,
we are on SRM 7.0 and ENHPack 4.0 and as you said its picking up the eSOA route to distribute contracts in backend ECC system.
I would like to know how can we this programmatically ( BADI / Enhancement points) and force system to pick the ALE/IDOC route ???
Do you know any BADI / Enhancement points where we can implement this ???

Could not connect to backend system through portal via Web Dispatcher

Web dispatcher redirecting problem
Dear Experts,
I have implemented a scenario which comprised of customizing that is developed in Portal EP7. What customizing does is getting report from backend system (ERP 6.0)
According to the needs for reaching the portal from internet I configured the SAP Web Dispatcher in the environment as you may see its contents below.
The problem is when I run the customizing in portal system then it requires connecting to backend system (ECC 6.0) to get the data (report). But from this point on web browser comes to a blank page, could not view the data that is from backend system via portal. Because in the time when it tries to retrieve data in backend system, on the left bottom of the explorer the indicator shows internet address that system uses connecting to the backend system as local network address of the backend system which is not known in internet therefore I get blank page.
The question is how to configure the web dispatcher in a way that both portal and backend systems could be reachable from internet?
Contents of profile file of Web Dispatcher as;
SAPSYSTEMNAME = WDP
SAPGLOBALHOST = portald
SAPSYSTEM = 02
INSTANCE_NAME = W02
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_CT_RUN)
Accesssability of Message Server
rdisp/mshost = portald
ms/http_port = 8101
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
SAP Web Dispatcher Ports
#icm/server_port_0 = PROT=HTTP,PORT=81$$
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=60000
icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
icm/HTTP/redirect_0 = PORT=50000
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
Regards,
Ali Taner

Hi,
To resovle this you must have registered FQDN for your backend system as well. When you call the report from Portal using internet it should call that FQDN of your backend system then DNS will resolve this & you will get the expected page. This way only you can resolve this issue.
Thanks,
Sachin Sable

MSS Component not connected with Backend system

Hello All,
In our NW Portal 7.01 system, we have got old Business package of MSS 60.1 & when we are trying to connect to our backend system R/3 4.7, we are able to connect it.
Now we have upgraded portal to EHP1 and then we are trying to do the same, then we are not able to connect to MSS business package, as we are getting TP Host missing error and connection not able to do with R/3 system
Has anyone come across such scenario? please update us asap.

Just 1 correction, we are able to work successfully with NW 7.0, but not after upgrade to EHP1.
So need to know, whether anyone is able to work with NW 7.01?

LDAP Userid not present in Backend System

We are trying to implement a scenario where the user are present in LDAP but are not present in the backend system "ECC".
Case Scenario: User log into portal using "testid" and want to access the BSP view which pull up the information from the backend system. Now this "testid" is not present in ecc system so i am looking for solution to achieve this scenario where "testid" will be able to pull the information without being created in ECC system.
This is required for our external customer which we donot want to setup in ecc system.
Any suggestion or if some one has implemented this scenario and can share how they did it will be really appreciated

Hi,
1.) Licensing. Noteably the first aspect that would come from SAP themselves will be licensing. You still need to be transparent about licensing with SAP in your scenario.
2.) Traceability. If any breaches are made or if any issues occur in yoru backend system, you will need to determine the exact time and it may be that the issue was invoked by several users acting on the system at the same time.
3.) Locking/Synch and Session Terminations. If mulitple users (using the same backend ID) perform update tasks on the database you may find that they will incur locking issues from trying to update the same record. Synchronous jobs may also result in issues similarly when invoked by different users on the same ID. Session management on the backend systems (dependant on the application) may also result in situations where multiple users may be limited to the max number of concurrent connections under their ID or sessions be "locked" as a result of terminations on the client side - which would require to be cleaned up from time to time.
While the above are some of the aspects that can be encountered, SAP generally handles these situations rather well, yet from a system managnment perspective you will encounter them from time to time.
PS: Depending on how you map users - individual mapping can become cumbersome particularly if mappings need to change etc. You can also map at a group level. This will make your life easy particularly say for vendors who have several employees yet need to map to one ECC ID to transact - just create a group per vendor assign the users to the group and map the group to the ID.
You can also us mass upload to map users efficiently - see:
http://help.sap.com/saphelp_nw72/helpdata/en/48/a96f43db653206e10000000a42189c/frameset.htm
https://cw.sdn.sap.com/cw/docs/DOC-107900
example:
[User]
uid=user0002
Last_Name=Johnson
$usermapping$:BCE:user=ext_user0002
$usermapping$:BCE:mappedpassword=initial1

Desirable Vendor not populating in backend (R/3)

Key Words: Desirable Vendor, Vendor Replication
System: SRM 5.0, SAP R/3 4.6
Scenario: Classic
We replicate vendors for the backend R/3 via BBPGETVD. However, when ran BBPGETVD we had some errors so we had to select If R/3 Number Assignment is not Possible. Internal Number Assignment.
We have set-up EBP and are able to create requisitions (PR) in the backend from the SCs. However, the PR that is created in the backend (R/3) the Preferred Vendor is not being populated even if we select a vendor in the Source of Supply section of the SC. The vendor number of the Vendor that is selected is not the vendor number is in the backend.
Could my problem of the Preferred Vendor not being populated because the vendor number does not match? i.e. the vendor number in EBP does not exist in R/3
If this is the case, what do I need to do to the vendor number in EBP so they match the vendors number in the backend.
I know that view BBPV_BUPA_VENMAP shows the mapping of the replicated vendor s in EBP to the vendors in R/3.
Any help, suggestions, etc. will be appreciated.
Thanks in advance.
Naing

Derek,
I ran BBPMAININT and made the changes.
You have to run the transaction in a new session
1) frist do /n in the Command field
2) then enter TCODE: BBPMAININT
3) then Manage Busines Partners will show
4) enter the serach for the BP and edit
5) screen to edid/amin the BP will appear
6) change to edite mode and make your changes and fill in all the required information. You will ahve to scroll down to find all the fields
7) scroll to the bottom and click on 'Vendor Data'. A new screen will appear....SCROLL to the bottom
8) near the bottom there is a tabel where you enter the Logical System, Vendor number (the R/3 vendor #)
hope that helps.
Naing
e-mail me at [email protected] if you have any additional questions
7)

Service Cofirmation not replicated in Backend system

Hi All,
When we are confirming service good in the SRM browser it is not being replicated in R/3, WS10400010 is being triggered and completed successfully but the data is not replicated in R/3.
I have checked the successful one and it has system status I1017,I1018 but the one which failed to replicate in R/3 has no statuses I1017 and I1018.
Can any one let me know what is the actual problem and what needs to be checked in R/3 whether the data is flowing or not.
Its urgent and every reply is hoghly appreciated.
Regards,
Ravi G

Hi Ravi,
Check in SLG1 & RZ20 (Application Monitors) for any error logs and detailed error description.
Check whether the programme BBP_GET_STATUS_2 is running properly in the back groung or not in the back ground.
In case the IDOC is getting failed check for the reason for failure of the IDOC in back end R/3 using WE05 / WE02 txn.
Please make the desired changes as per the IDOC failure message and reprocess the IDOC.
Hope this will make you clear about the issue. Clarifications are welcome.
Do update us for further help.
Award points for helpful answers.
Rgds,
Teja

'Backend systems with Release 701 are not supported'

while BBPGETVD transaction is run below error is seen,
'Backend systems with Release 701 are not supported'
Please help to resolve it.

Hi
What is your backend system ECC version?
What is the configuaration in Define back end system?
Note 1313972 - BBPGETVD: Backend system latest release not supported
br
muthu

Goods Receipt not transferred to the Backend System R/3

We are currently using BBPCRM4.0 & SAP R/3 4.7 (extended scenario)
For a particular Purchase Order which has a material number, We cannot transfer GR to the Backend System R/3 successfully.(The shopping cart of unsuccessfully transferred GR is created by using material)
When I check R/3 using WE05, I can find the message "The plant data of the material G09002202 is locked by the user MRP_RFC". This must be the reason why GR is not transferred successfully to the Backend System, but I do not know what this message mean.(As you see, MRP_RFC is the user name that connects SRM and R/3. + That moment the material is not locked by any user in R/3)
If we try to create the GR document again in SRM, the message "Item is already being processed" is shown, so cannot make BUS2203 Docs.
To sort out this, we remove the GR Transfer Error Information in
BBP_DOCUMENT_TAB.
After removing the information of this error in BBP_DOCUMENT_TAB, surprisingly we can make GR successfully.
Weird!.
Only for a particular PO which has a material, but not everytime.
Sometimes this problem happens.
At the first time, it doesn't work, but after removing the data from BBP_DOCUMENT_TAB, when we try GR again it works.
Could you help me why this symptom happends..?
Edited by: Hyangsook Moon on Feb 28, 2008 6:44 AM

Hi Hyangsook Moon,
The system is allowing you to create Confirmation again in SRM because the status is not yet updated in SRM since the G.R is not created in the backend successfully.
Since the confirmation is created in SRM and could not able to create G.R in R/3 through IDOC the system is giving you message as " Document is being processed".
So the system is allowing you to create confirmation again once you delete the table entry.
Hope this makes you more clear.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

JDBC Adapter - DELETE operation not working in receiver backend system

Hi All,
In my scenario ,I want to delete entire records of the table from one backend system.
I have created the inbound message and after mapping it is as below:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:abc_delete xmlns:ns0="http://abc/xi/BACKEND/IB_IF_18/100">
<STATEMENTNAME>
<F12345 action="DELETE" />
</STATEMENTNAME>
</ns0:abc_delete>
here F12345 is the table name.
When I execute this scenario I get black and white flag in XI SXMB_MONI but in backend system (SQL Server) no records get deleted the table is as it is.

Please have a look on this (same mentioned by Bhavesh)...
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/frameset.htm
 <StatementName3>
<dbTableName action=DELETE>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
<key2>
<col2>val2old2</col2>
</key2>
</dbTableName>
</StatementName3>
● action=DELETE
Statements with this action cause existing table values to be deleted. One or more <key> elements formulate the condition for which table values are deleted. The names of <key> elements are arbitrary. Column values within a <key> element are combined with a logical AND; different <key> elements are combined with a logical OR.
The corresponding SQL statement for StatementName3 in the example above is as follows:
DELETE FROM dbTableName WHERE ((col2=val2old AND col4=val4) OR (col2=val2old2))
The response document contains the following element:
<delete_count>count</delete_count>
If there is no <key> element, or if there is a <key> element but it is empty, then no condition is specified and the entire table is to be deleted. This may not be permitted by the configuration of the JDBC adapter for security reasons and will therefore result in an error during message processing and an appropriate error message.
Thanks
Farooq.

Backend System with Release 701 are not supported

SRM 5.0
Extended Classic Scenario
CCM 2.0
When updating the vendors in SRM system using TC - BBPUPDVD getting the below error message :-
Backend System with Release 701 are not supported
Have checked in table - BBP_BACKEND_DEST, the backend entry is properly maintained.
Can any one advice.
Regards,
Jayoti
Edited by: SAP jayoti on Dec 7, 2010 1:11 PM

The problem is resolved for vendor relication after applying the below notes 1313972 and 1372175.
ECC sandbox seems to be in 701 release. When the backend system ECC is in release 701, vendor replication fails with the error message that 'Backend system release 701 not supported'. We need to apply notes 1313972 and 1372175 to fix this issue. I have applied them in Sandbox and the issue is resolved now.

Not able to do user Mapping with the backend System

Hello all,
I am trying to Map a user to a windows based KM System but getting an error like
"There is a configuration issue which leads to problems when accessing user mapping data for the selected backend system 'KM_Test_System'. Usually, the reason is user mapping being configured for strong encryption, but the necessary additional files being missing. Check the security log file for further information and hints on how to solve the problem."
Can somebody tell me what could be the possible reason for this and how to handle this. I dont have access to the Portal server right now , so not able to see the security log.
Thanks to all,
Regards,
Sarabjeet Singh.

Hi Sarbjeet,
I believe this links will help you understand and solve your problem:
user mapping is not saved
and
http://help.sap.com/saphelp_nw04/helpdata/en/04/d246215f1d4f588d1d9c49391acb01/frameset.htm
Hope this helps,
Robert

Some POs are not generated in the backend system

Hi,
we've implemented SAP SRM 5.5. in a Classic Extended Scenario with SAP R/3 as the backend system.
Recently we are facing a problem related to some Purchase Orders. If they have some wrong information for the backend system, they do not get the "Error in process" status but the are put in the "Ordered" status even though they are not replicated in SAP R/3.
This problems occurs only with some POs and only (for as much as we could see) if the PO has been generated from an Offer (S.C.->Bid Invitation->Offer->PO).
Could you please help me out with this issue? I can't understand why this is happening...
Thanks a lot for your precious advices!
Giovanni

Hi Sanjeev,
thanks for your quick reply. I've checked the RZ20 and there's an error message related to the Header Data. I've checked also the PO from BBP_PD and I could see that in table BBP_PDIGP the EP subtype is missing. If I force it and then I transfer the PO again, everything is fine.
I can't understand why this is happening. I've never had any problems like that with other POs created straight out of a S.C.. The issue is related only with POs created out of a Bid.
Please, let me know if you have an idea.
Have a nice day!
Giovanni

System not populating any report in V_UC

Hi all,
i am runing report Incomplete Outbound Deliveries V_UC system not populating report can any one guide me where i am wrong
while executing V_UC report.
Thanks
Ram

Hi,
Goto the t.code "V_UC".
Ensure that correct SD document category is selected in the selection screen.
Select I for "Order" or "J" for delivery etc...
Goto the T.Code "0VLK".Select your delivery type.Details.
Check what is the document category assigned to it.
Maintain the same in "V_UC".
Execute.
Regards,
Krishna.

BBPGETVD - error:backend systems with release 700 are not supported

Hi,
When I am trying to replicate vendor data from EEC to crm 4.0 via BBPGETVD.
I get the error message"backend systems with release 700 are not supported"
Is anyone have Idea what is wrong? and how can fix it?
Thanks,
Rachel

Yossi,
I believe that standard transaction does not work with ECC 6.0. The standard response would be to upgrade your CRM system to 5.0 so that you can download vendors from ECC 6.0.
Bascially the vendor replication programs in CRM below 5.0 aren't really that reliable for delta downloads(one error will cause an entire load to fail). So you probably at best should copy the SAP standards to generate custom load programs as a starting point.
It is not too difficult and overcomes some of the restrictions that SAP puts in place(i.e. you can only use one number range for vendors downloaded, etc.). This is definitely one of the weak points of CRM 4.0 that was fixed in CRM 5.0.
If you have more questions on this let me know.
Take care,
Stephen

PO is not populated to backend system

Similar Messages

Maybe you are looking for