ECC -- PI -- SRM via proxies

Hi All,
We have are working on SAP ECC via PI to SRM and SUS systems through proxies.
Now there is a requirement that we need to include some zfields to the existing std. structures of the proxies at SRM and in ECC. So could you please advice me how to go about it, as the std structure comes with all pre defined DT, MT, MM, OM etc (ie with all ESR objects). Now if I have do the customization to this struture by including the new fields in the source and target structures how do I do that.
These DT and MM has so many inter-related DT and functions (UDFs) respectively which I am not able to edit in the std SWCV, so should I copy all these into another SWCV and start working on it or is there any other way.
Please share your thoughts.
Regards,
Nithiyanandam

Hi
if the nproxy has a badi associated what you need to do is create a new enhancement DT in the ESR, when you define this kind of DT, one of the configuration fields is to define the segment of the standard DT you want to Extend.
once you did that, goto SE80 in your sap system, search the DT enhancement proviuosly right button --> Create proxy
once created-->Activate
The system create and append structure in the standard structure
you need to know if the standard proxy has a BADI associated. if not you cannot extend it. (see SAP workplace and search for your service or by customazing SPRO Tcode)
then search for the BADI
take in mind that Badis has two sight
definition and implementation:
in Tcode SE18 you will see the definition (input output parameters, badi type, etc)
in Tcode SE19 you cann see all the implementation of the selected Badi
search in SDN about Enhancement Data Type and how to Extend standard proxys to more information.
Thanks
Rodrigo P-.
Edited by: Rodrigo Alejandro Pertierra on May 31, 2011 12:09 PM

Similar Messages

Pushing Purchase Requisition from ECC to SRM via XI in PPS

Dear Experts,
Environment SRM 7.0 ECC 6.0 ep4 and PPS 33.0
We are having an issue with pushing the Purchase Requisitions from ECC to SRM 7.0 via XI using the SOA. There is an Application error on the receiving side in SRM (Faulty exchange Data) when pushing the PR from XI to SRM using the inbound interface Purchasing RequestERPSourcing_In. The outbound interface from ECC to Xi PurchasingRequest_ERPSourcing_Out is working fine without any errors.
Please let me know if any one has similiar issues in a PPS public sector implementation and any resolutions?
Thanks in advance for the help,
Scott

HI ,
If you have the xml in srm having status "Transfer to external application" then you can use the Forward Error Handling (FEH) concept in SOA. If you have done the required configuration for FEH and use transaction /n/SAPPO/PPO2 in SRM you will be able to see the actual error why xml is failing. Also rememeber to change the value for field Mode of postprocessing Order to 0 in the screen you get after running tranaction /n/SAPPO/PPO2
To configure FEH refer note: 1270081
Hope this helps.
Regards
Sam
Edited by: Sam Chacko Ninan on Feb 12, 2010 10:06 AM

Purchase Requisition transfer from ECC to SRM via XI

Experts,
Please let me know if you have any information on the following issue:
Environment : SRM 7.0, ECC ep4, Extended Classic scenario
The purchase requisitions have been created in ECC and released. I believe in SRM 7.0 the PR's get automatically transferred to SRM Sourcing cockpit via XI from ECC.
One PR was pushed manually from SMQ1(Outbound queue ) in ECC and this failed due to a login issue in XI.
The XI was using the interface PurchaseRequestERPSourcingRequest.
My question is
1. When the PR is released in ECC, where to check if the PR is pushed to XI. Do we need to schedule a job? When I checked SMQ1 (outbound queue, the queues are empty)
2. Do we need to define the partner profile in ECC for XI in We20. If so, then what message types to use for the IDocs going from ECC to XI.
2. Do we need to configure the interface PurchaseRequestERPSourcingRequest in XI to map the incoming PR from ECC.
3. In transaction SXMB_moni in XI I am not able to pull the XML messages. What options options do I need to
set to pull the messages that errored out.
Thanks,
Scott.

Hi All,
Hope this helps you for XI configuration
Importing Business Scenarios for Sourcing
In this section, you transfer the business scenario Strategic Sourcing from the SAP Integration Repository, generate it, and activate it.
Prerequisites
You have:
Defined the business systems for SAP Supplier Relationship Management (SAP SRM) and SAP ERP in the SAP System Landscape Directory. For more information about SAP NetWeaver Process Integration (SAP NetWeaver PI), see the SAP Marketplace
Imported the SAP NetWeaver PI content for SAP SRM into the SAP Integration Repository.
Procedure
Log on to the SAP Netweaver PI system.
Choose Integration Builder: Configuration.
In the left pane, select the Objects tab.
Choose Service Without Partner Business System .
Right-click to display the context menu and choose Business Systems Assign Business System . This opens the wizard.
Choose Continue. The wizard guides you through the required steps.
Create the business system for both SAP SRM and ERP (you can bypass this step if the business system is already setup).
Select a business system.
You can create communication channels either manually or automatically. You can create them automatically here. In this case, the systems are applied from the SAP System Landscape Directory (SLD). Channels must be complete in terms of URLs and authentication information.
Choose Finish, and then choose Close.
11. On the main screen, choose Tools Transfer Integration Scenario from Integration Repository . This opens a wizard.
Choose Name using input help SE_Sourcing_Enhancements
Choose Continue. The scenario name is SE_Sourcing_Enhancements.
Choose Finish and then choose Close. The Business Scenario Configurator opens automatically.
Choose Component View.
The Select Component View window opens.
Choose Apply.
Choose Assign Services. The Assign Services to Application Component window opens.
Press F4 to retrieve the available services.
Choose Assign.
Select the related service and choose OK.
Assign a business service to all roles.
Choose Configure Connections.
Select the connections from the Service Assignment tab.
Press F4 in the Communication Channel field.
Select a communication channel. This channel must be of type XI.
Note
If the systems are applied from the SAP Landscape Directory, the Integration Builder automatically creates the communication channels.
If the systems are not applied from the SAP Landscape Directory, you create communication channels manually. To do this choose an existing service and then Communication Channel using context menu New. You must assign a communication channel for each connection.
End of the note.
Choose OK and then choose Apply.
Choose Generate to open the Create Configuration Objects window.
Choose Simulation, then Generate, then mark all in the list Scope of Generation.
Choose Start to generate a log. Check the log for errors and save it if required.
In the Close Integration Scenario screen, choose Apply.
In the left pane, select the Scenarios tab; your scenario has been added.
In the left pane, select the Change List tab.
Expand the Standard Change List.
Right click on the scenario name SE_Sourcing_Enhancements and choose Activate.
Regards
Sam

ECC - XI - SRM : Successfully sent but BP not getting created

Hello XI Experts,
We are integration ECC and SRM via XI.
Now we are implementing PDP (Process Driven Procurement) scenario and are sending CREMAS03 idoc ( that is Vendor) to SRM system.
THe message is showing success in SXMB_MONI in both XI and SRM box.
However no Business Partner is getting created in SRM system(Transaction bp).
Can someone throw any light on this.
A Few more informattion:
SRM side there is an inbound proxy for the inbound interface:
SupplierPortalTradingPartner_CreateOrChange_In
(http://sap.com/xi/SRM/SupplierEnablement)
Implementing Class: CL_BBPX_TRADING_PARTNER_SUS_IN
Proxy Interface: II_BBPX_TRADING_PARTNER_SUS_IN
Cheers,
Himadri

Tuhin,
I have executed the Proxy standalone by populating the payload and it is successful - then also no BP got created.
Any idea --
One more thing I want to increase the trace level in SXMB_Moni -- that is because the steps that are showing are Receiver determination -- Then Response ... and it is ommitting the display of Logical Routing / Technical routing...
Can you suggest how to set that?
Cheers,
Himadri

PR and PO creation in ECC from SRM 7.0

Hi everyone,
I have a pair of doubt. We are planning to upgrade SRM 3.0 to SRM 7.0 with ECC 6.0 ep 4 in a classic scenario. My doubts are:
1.- Can we create a PR from a SC using PI by standard or is the same as the previous version (using RFC)??
2.- Can we create a PO from a SC using PI by standard or is the same as the previous version (using RFC)??
3.- We checked the documentation and there is a different type of contract, the central contract. This contract can be transfer to ECC?? if yes, is it transferred using PI??
Thanks,
Ivá

Purchase Requisition transfer from ECC to SRM via XI
Hi Ivan
for self service procurement XI is not required .sorry for the confusion.
please see the donald reply here
XI is mandaory in PDP .
SRM 550 - no required in PDP.
Here there is no BBP TRANSFER job.
Automatically done .
Thanks
Muthu

ECC to SRM Issue

Hi experts,
we are doing ECC to SRM Integartion using SAP XI.
ECC to XI - IDOC
XI to SRM - ABAP Proxies
Scenario : VEndor data migaration
We are transfering vendor data to SRM using SAP XI using BD14 T.code in ECC.
IDOC generated in ECC and transfered to XI successfully and from XI message send to SRM successfully. In SRM , It is throwing an error in SXMB_MONI .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As we used CREMAS As IDOC in ECC and Standard ABAP proxy ( Std class ) at SRM side.
as i tested the class manually it is throwing into dump.
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception CX_SY_REF_IS_INITIAL
Date and Time 13.12.2008 17:36:42
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_PROXY_INBOUND_ADAPTER======CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "SET_METHOD" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
"CL_PROXY_INBOUND_ADAPTER======CP" or "CL_PROXY_INBOUND_ADAPTER======CM00I"
"SET_METHOD"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SET_METHOD" "(METHOD)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "SRMSUS"
Network address...... "190.3.90.122"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SRMSUS"
Database type..... "ORACLE"
Database name..... "SRD"
Database user ID.. "SAPSRD"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Oct 6 2008 01:42:27"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 180
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 18815328
Heap.... 0
Page.... 114688
MM Used. 2421664
MM Free. 712664
User and Transaction
Client.............. 500
User................ "MCL-1744"
Language key........ "E"
Transaction......... "SPROXY "
Transactions ID..... "7C0EC9DD9C02F137A21C00065BF30D3E"
Program............. "CL_PROXY_INBOUND_ADAPTER======CP"
Screen.............. "SAPLSPRX_SI_TEST 0500"
Screen line......... 10
Information on where terminated
Termination occurred in the ABAP program "CL_PROXY_INBOUND_ADAPTER======CP" -
in "SET_METHOD".
The main program was "SPROX_SERVICE_INTERFACE_TEST_I ".
In the source code you have the termination point in line 59
of the (Include) program "CL_PROXY_INBOUND_ADAPTER======CM00I".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "SET_METHOD" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_PROXY_INBOUND_ADAPTER======CP "; its source
code begins in line
1 of the (Include program "CL_PROXY_INBOUND_ADAPTER======CM00I ".
Source Code Extract
Line
SourceCde
29
nsuri = lv_uri
30
31
32
lv_name = registry->response_msg_name.
33
lv_uri = registry->response_msg_namespace.
34
me->response_part = cl_sxmlp_factory=>create_data_st(
35
name = lv_name
36
nsuri = lv_uri
37
38
39
lv_extended_xml_handling = get_extended_xml_handling(
40
method = me->framework->if_proxy_framework~r3_method
41
message_direction = if_wsprotocol_payload=>co_message_direction_request
42
43
lr_stylesheet_runtime = framework->get_stylesheet_runtime( lv_extended_xml_handling ).
44
45
lt_signature = lr_stylesheet_runtime->get_signature( ).
46
loop at lt_signature assigning <signature>.
47
if <signature>-decl = sprox_const_dir_importing or
48
<signature>-decl = sprox_const_dir_exporting or
49
<signature>-decl = sprox_const_dir_changing.
50
 create abap data
51
create data lr_data_ref type (<signature>-typename).
52
 add it to abap parameters
53
lv_abap_param-name = <signature>-param.
54
lv_abap_param-value = lr_data_ref.
55
insert lv_abap_param into table abap_params.
56
case <signature>-decl.
57
 add it to according part
58
when sprox_const_dir_importing.
>>>>>
me->request_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref ).
60
when sprox_const_dir_exporting.
61
me->response_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref )
62
lv_need_response_part = 'X'.
63
when sprox_const_dir_changing.
64
me->request_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref ).
65
me->response_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref )
66
lv_need_response_part = 'X'.
67
endcase.
68
endif.
69
endloop.
70
71
me->is_synchron = lv_need_response_part.
72
73
if lv_need_response_part <> 'X'.
74
response part must not be provided for there are no output parameters
75
clear me->response_part.
76
endif.
77
78
make sure that proxy class is created
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
MAIN
SY-UCOMM
SY-TITLE
Test Service Provider: Display Request
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
2
SY-DATUM
20081213
SY-UZEIT
173642
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
9 METHOD CL_PROXY_INBOUND_ADAPTER======CP CL_PROXY_INBOUND_ADAPTER======CM00I 59
CL_PROXY_INBOUND_ADAPTER=>SET_METHOD
8 METHOD CL_PROXY_INBOUND_ADAPTER======CP CL_PROXY_INBOUND_ADAPTER======CM00L 10
CL_PROXY_INBOUND_ADAPTER=>IF_PROXY_INBOUND_ADAPTER~SET_METHOD
7 METHOD CL_PROXY_ADAPTER_TEST=========CP CL_PROXY_ADAPTER_TEST=========CM001 61
CL_PROXY_ADAPTER_TEST=>INBOUND_TEST
6 METHOD SPROX_SERVICE_INTERFACE_TEST_I SPROX_SERVICE_INTERFACE_TEST_I 162
LCL_SI_TEST=>IF_PROXY_SI_TEST~EXECUTE
5 FORM SAPLSPRX_SI_TEST LSPRX_SI_TESTF01 341
EXEC
4 FORM SAPLSPRX_SI_TEST LSPRX_SI_TESTF01 222
USER_COMMAND_0500
3 MODULE (PAI) SAPLSPRX_SI_TEST LSPRX_SI_TESTI01 22
USER_COMMAND_0500
2 FUNCTION SAPLSPRX_SI_TEST LSPRX_SI_TESTU01 14
SPRX_SI_TEST
1 EVENT SPROX_SERVICE_INTERFACE_TEST_I SPROX_SERVICE_INTERFACE_TEST_I 97
START-OF-SELECTION
Chosen variables
Name
Val.
No. 9 Ty. METHOD
Name CL_PROXY_INBOUND_ADAPTER=>SET_METHOD
REGISTRY
E0001000
2000D100
REQUEST_PART
|
| F0000000 |
| F0000000 |
| LT_SIGNATURE |
| Table IT_894[1x879] |
| CLASS=CL_PROXY_INBOUND_ADAPTERMETHOD=SET_METHODDATA=LT_SIGNATURE |
| Table reference: 90 |
| TABH+ 0(20) = E078CC51C827D051000000005A0000007E030000 |
| TABH+ 20(20) = 010000006F0300004800000004D30000A80F0000 |
| TABH+ 40( 8) = 10000000C1048401 |
| store = 0xE078CC51 |
| ext1 = 0xC827D051 |
| shmId = 0 (0x00000000) |
| id = 90 (0x5A000000) |
| label = 894 (0x7E030000) |
| fill = 1 (0x01000000) |
| leng = 879 (0x6F030000) |
| loop = 72 (0x48000000) |
| xtyp = TYPE#000061 |
| occu = 16 (0x10000000) |
| access = 1 (ItAccessStandard) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 2 (ItUniqueNon) |
| keyKind = 1 (default) |
| cmpMode = 2 (cmpSingleMcmpR) |
| occu0 = 0 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0xD81DD151 |
| pgHook = 0x00000000 |
| idxPtr = 0x00000000 |
| shmTabhSet = 0x00000000 |
| id = 713 (0xC9020000) |
| refCount = 1 (0x01000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 16 (0x10000000) |
| lineAlloc = 16 (0x10000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 2 (0x02000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = 0xB8FDCF51 |
| collHook = 0x00000000 |
| ext2 = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| <SIGNATURE> |
| INTFII_BBPX_TRADING_PARTNER_SUS_INMETHEXECUTE_ASYNCHRONOUS INPUT |
| 4454445445555544444554554455555544445445445545455444544455222222222244555222222222222222222222 |
| 9E4699F2208F42149E7F0124E52F353F9ED5485853545F139E382FEF5300000000009E054000000000000000000000 |
| CL_WS_MD_FACTORY=>PROFILE_STATELESS_BASIC_AUTH |
| ??? |
| ?????? |
| ?????? |
| <SIGNATURE>-DECL |
| 0 |
| 3 |
| 0 |
| SPROX_CONST_DIR_IMPORTING |
| 0 |
| 3 |
| 0 |
| SYST-REPID |
| CL_PROXY_INBOUND_ADAPTER======CP |
| 4455545554444544544455453333334522222222 |
| 3CF02F89F9E2F5E4F1410452DDDDDD3000000000 |
| SPROX_CONST_DIR_EXPORTING |
| 1 |
| 3 |
| 1 |
| SPROX_CONST_DIR_CHANGING |
| 2 |
| 3 |
| 2 |
| CL_WB_REQUEST=>WN_SAME_WINDOW |
| ??? |
| ?????? |
| ?????? |
| LR_DATA_REF |
| 0.0.0.0.0.0.0.1. |
| 6000A000 |
| C0003000 |
| <SIGNATURE>-TYPENAME |
| BBPX_TRADING_PARTNER_SUS |
| 445555544444554554455555222222 |
| 2208F42149E7F0124E52F353000000 |
| SY-XPROG |
| SAPMSSY1 |
| 5454555322222222222222222222222222222222 |
| 310D339100000000000000000000000000000000 |
| LV_ABAP_PARAM-VALUE |
| 0.0.0.0.0.0.0.1. |
| 6000A000 |
| C0003000 |
| ME->ABAP_PARAMS |
| Table IT_895[1x40] |
| DATA=ABAP_PARAMS
Table reference: 91
TABH+ 0(20) = 2003D05100000000000000005B0000007F030000
TABH+ 20(20) = 0100000028000000FFFFFFFF04D3000058070000
TABH+ 40( 8) = 10000000A4258001
store = 0x2003D051
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 91 (0x5B000000)
label = 895 (0x7F030000)
fill = 1 (0x01000000)
leng = 40 (0x28000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000023
occu = 16 (0x10000000)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x9000D051
pgHook = 0x00000000
idxPtr = 0x6003D051
shmTabhSet = 0x00000000
id = 714 (0xCA020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LV_ABAP_PARAM
INPUT #l###£###
445552222222222222222222222222206000A000
9E054000000000000000000000000000C0003000
SY-REPID
CL_PROXY_INBOUND_ADAPTER======CP
4455545554444544544455453333334522222222
3CF02F89F9E2F5E4F1410452DDDDDD3000000000
SY
############################################################################o#################
0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
<SIGNATURE>-PARAM
INPUT
445552222222222222222222222222
9E0540000000000000000000000000
SCREEN
TAB_CONTROL_TAB4
5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 8 Ty. METHOD
Name CL_PROXY_INBOUND_ADAPTER=>IF_PROXY_INBOUND_ADAPTER~SET_METHOD
INTERFACE
II_BBPX_TRADING_PARTNER_SUS_IN
445445555544444554554455555544
99F2208F42149E7F0124E52F353F9E
METHOD
EXECUTE_ASYNCHRONOUS
454455454554445444552222222222
5853545F139E382FEF530000000000
REQUEST_PART
|
| F0000000 |
| F0000000 |
| LR_REGISTRY |
|
E0001000
2000D100
ME
|
| E0001000 |
| 90006100 |
| No. 7 Ty. METHOD |
| Name CL_PROXY_ADAPTER_TEST=>INBOUND_TEST |
| INTERFACE |
| II_BBPX_TRADING_PARTNER_SUS_IN |
| 445445555544444554554455555544 |
| 99F2208F42149E7F0124E52F353F9E |
| METHOD |
| EXECUTE_ASYNCHRONOUS |
| 454455454554445444552222222222 |
| 5853545F139E382FEF530000000000 |
| RUNTIME |
| RUNTIME_TEST |
| 554544455455 |
| 25E49D5F4534 |
| REQUEST_DATA |
| <n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx |
| 3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777 |
| CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028 |
| DONT_CATCH_APPL_FAULT |
| |
| 2 |
| 0 |
| RESPONSE_DATA |
| |
| ERROR_DATA |
| |
| EXCEPTION_CLASS_NAME |
| |
| RUNTIME_SERIALIZE |
| 0 |
| 0000 |
| 0000 |
| RUNTIME_DESERIALIZE |
| 0 |
| 0000 |
| 0000 |
| RUNTIME_EXECUTE |
| 0 |
| 0000 |
| 0000 |
| INBOUND_ADAPTER |
|
E0001000
90006100
LR_PAYLOAD_PROTOCOL
|
| E0001000 |
| 4000B100 |
| %_FSREG_001 |
| ??? |
| ?????? |
| ?????? |
| LR_REQUEST_PAYLOAD |
|
E0001000
3000C100
%_DUMMY$$
2222
0000
%_SPACE
2
0
SYST
############################################################################o#################
0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
SYST-REPID
CL_PROXY_ADAPTER_TEST=========CP
4455545554445545554553333333334522222222
3CF02F89F1410452F4534DDDDDDDDD3000000000
LR_REQUEST_PART
F0000000
F0000000
LV_RUNTIME_0
0
0000
0000
SY-REPID
CL_PROXY_ADAPTER_TEST=========CP
4455545554445545554553333333334522222222
3CF02F89F1410452F4534DDDDDDDDD3000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
LR_READER
F0000000
F0000000
No. 6 Ty. METHOD
Name LCL_SI_TEST=>IF_PROXY_SI_TEST~EXECUTE
REQUEST
<n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx
3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777
CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028
RESPONSE
CALL_FAILED
2
0
RUNTIME_SERIALIZE
0
0000
0000
RUNTIME_DESERIALIZE
0
0000
0000
RUNTIME_EXECUTE
0
0000
0000
%_DUMMY$$
2222
0000
SCREEN
TAB_CONTROL_TAB4
5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
SY
############################################################################o#################
0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
ME->INTERFACE
II_BBPX_TRADING_PARTNER_SUS_IN
445445555544444554554455555544
99F2208F42149E7F0124E52F353F9E
ME->METHOD
EXECUTE_ASYNCHRONOUS
454455454554445444552222222222
5853545F139E382FEF530000000000
ME->NO_CATCH
2
0
LV_ERROR_DATA
ME->EXCEPTION_CLASS_NAME
%_VIASELSCR
0
4
RSJOBINFO
00000000000000 ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LR_APPL_FAULT
|
| F0000000 |
| F0000000 |
| %_SPACE |
| |
| 2 |
| 0 |
| No. 5 Ty. FORM |
| Name EXEC |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| GR_REQUEST |
|
4000B000
70008000
SPACE
2
0
REQUEST_DATA
<n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx
3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777
CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028
GR_CALL_FAILED
2
0
RESPONSE_DATA
LV_RUNTIME_SERIALIZE
0
0000
0000
LV_RUNTIME_DESERIALIZE
0
0000
0000
LV_RUNTIME_EXECUTE
0
0000
0000
CL_GUI_CONTROL=>LIFETIME_DEFAULT
0
0000
0000
SYST-REPID
SAPLSPRX_SI_TEST
5454555555455455222222222222222222222222
310C3028F39F4534000000000000000000000000
SCREEN
TAB_CONTROL_TAB4
5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 4 Ty. FORM
Name USER_COMMAND_0500
SY-REPID
SAPLSPRX_SI_TEST
5454555555455455222222222222222222222222
310C3028F39F4534000000000000000000000000
LV_OKCODE
EXEC
4544222222222222222222222222222222222222222222222222222222222222222222
5853000000000000000000000000000000000000000000000000000000000000000000
GV_SAMPLE_RESPONSE_PAYLOAD
%_SPACE
2
0
G_TAB_CONTROL-PRESSED_TAB
REQUEST
5455455222222222222222222222222222222222222222222222222222222222222222
2515534000000000000000000000000000000000000000000000000000000000000000
GR_RESPONSE
|
| 5000A000 |
| D0002000 |
| %_VIASELSCR |
| # |
| 0 |
| 4 |
| SY-XPROG |
| SAPMSSY1 |
| 5454555322222222222222222222222222222222 |
| 310D339100000000000000000000000000000000 |
| No. 3 Ty. MODULE (PAI) |
| Name USER_COMMAND_0500 |
| %_PRINT |
| 000 0 ## |
| 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 2 Ty. FUNCTION |
| Name SPRX_SI_TEST |
| SI_TEST |
|
F0000000
C0003000
G_TAB_CONTROL
0600SAPLSPRX_SI_TEST REQUEST
3333545455555545545522222222222222222222222254554552222222222222222222222222222222222222222222
0600310C3028F39F453400000000000000000000000025155340000000000000000000000000000000000000000000
GR_SI_TEST
|
| F0000000 |
| C0003000 |
| GV_CANCELED |
| |
| 2 |
| 0 |
| ABAP_FALSE |
| |
| 2 |
| 0 |
| SY-XFORM |
| XAB_READ |
| 544554442222222222222222222222 |
| 812F25140000000000000000000000 |
| GR_CONTAINER |
|
4000B000
90006000
GR_REFERENCE
|
| 80007000 |
| 0000F000 |
| GR_DIFF |
|
80007000
3000C000
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-SUBRC
0
0000
0000
SY-REPID
SPROX_SERVICE_INTERFACE_TEST_I
5554555455444544545444455455542222222222
302F8F3526935F9E4526135F4534F90000000000
SY-MSGID
22222222222222222222
00000000000000000000
SPACE
2
0
SY-MSGNO
000
333
000
%_P_INTF_%_APP_%
Interface Name
467676666246662222222222222222
9E45261350E1D50000000000000000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
LR_SI_TEST
F0000000
C0003000
R3NAME
II_BBPX_TRADING_PARTNER_SUS_IN
445445555544444554554455555544
99F2208F42149E7F0124E52F353F9E
METHOD
222222222222222222222222222222
000000000000000000000000000000
%_P_METH_%_APP_%
Method Name
467666246662222222222222222222
D548F40E1D50000000000000000000
Internal notes
The termination was triggered in function "method_call_iref"
of the SAP kernel, in line 2207 of the module
"//bas/700_REL/src/krn/runt/abmethod.c#10".
The internal operation just processed is "METH".
Internal mode was started at 20081213173634.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=4716)
When : 12/13/2008 17:36:42.685
Threads : 2
Computer Name : SRMSUS
User Name : SAPServiceSRD
Number of Processors: 4
Processor Type: x86 Family 15 Model 2 Stepping 7
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 1288
eax=000fb648 ebx=000003a8 ecx=00000038 edx=00000000 esi=000003a8 edi=00000000
eip=7c8285ec esp=0465dc9c ebp=0465dd0c iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c8285ec c3 ret
7c8285ed 8da42400000000 lea esp,[esp] ss:0465dc9c=7c827d0b
7c8285f4 8d642400 lea esp,[esp] ss:2266ccaf=????????
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0465dd0c 77e61c8d 000003a8 0001d4c0 00000000 0465dd44 ntdll!KiFastSystemCallRet
0465dd20 01066cf4 000003a8 0001d4c0 00000001 7c3ab718 kernel32!WaitForSingleObject
0465dd44 00585f0e 00585f47 7c3ab718 7c3ab718 7c3ab718 disp+work!NTDebugProcess
0465dd48 00585f47 7c3ab718 7c3ab718 7c3ab718 01ca73bc disp+work!NTStack
0465dd64 00585f7b 7c3ab718 00000000 008acf08 7c3ab718 disp+work!CTrcStack2
0465dd70 008acf08 7c3ab718 00000000 32305f59 39303030 disp+work!CTrcStack
0465dd8c 008b02dd 51cf3fd0 00008002 00000000 51b20548 disp+work!rabax_CStackSave [abrabax.c (7125)
0465e220 006d1f09 012ca01c 012c9ffc 0000089f 01d0bfc0 disp+work!ab_rabax
0465e250 006e2868 00000003 51c99e30 00000000 0465e2b8 disp+work!method_call_iref [abmethod.c (2207
0465e2b8 0081cecf 00000000 51c99e30 0465e308 51c9af4d disp+work!ab_extri
0465e2cc 0088eecd 00000000 51c9ad56 005c5927 51c9a814 disp+work!ab_xevent
0465e2d8 005c5927 51c9a814 00000022 51c9ad56 00000000 disp+work!ab_dstep
0465e380 005c8c7f 51c99e30 51c99e30 0465fd4c 00000000 disp+work!dynpmcal
0465e394 005c82a0 51c99e30 51c99e30 00000003 0465fd4c disp+work!dynppai0
0465e3b0 0059a493 51c99e30 00000003 00000001 00000001 disp+work!dynprctl
0465fdc0 00494f08 00000002 004a167e 00000002 00000000 disp+work!dynpen00
0465fdc8 004a167e 00000002 00000000 00000003 00000002 disp+work!Thdynpen00
0465fee4 004a1bfb 002463f8 00000001 00000000 01bca464 disp+work!TskhLoop
0465ff00 004237f9 00000000 00000000 7ffde000 0465ff60 disp+work!ThStart
0465ff14 0040108a 00000003 002463f8 00000001 00000000 disp+work!DpMain
0465ff60 0122a2c0 00000003 002463f8 00242ca0 01b69000 disp+work!nlsui_main
0465ffc0 77e6f23b 00000000 00000000 7ffde000 00000000 disp+work!mainCRTStartup
0465fff0 00000000 0122a17d 00000000 00000000 00000000 kernel32!ProcessIdToSessionId
State Dump for Thread Id 1340
eax=00000001 ebx=00000103 ecx=7c829f59 edx=004b0000 esi=00000000 edi=00000000
eip=7c8285ec esp=06aafec0 ebp=06aaff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c8285ec c3 ret
7c8285ed 8da42400000000 lea esp,[esp] ss:06aafec0=7c8270fb
7c8285f4 8d642400 lea esp,[esp] ss:24abeed3=????????
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
06aaff04 0116fba0 00000694 00000000 00000000 002481d8 ntdll!KiFastSystemCallRet
06aaff84 7c36b381 00000000 00000000 00000000 00248140 disp+work!SigIMsgFunc
06aaffb8 77e64829 00248140 00000000 00000000 00248140 MSVCR71!endthreadex
06aaffec 00000000 7c36b312 00248140 00000000 00000000 kernel32!GetModuleHandleA
List of ABAP programs affected

Dear Ashok,
Please follow the below steps then it should work.
1. Call transaction BBP_SUS_BP_ADM to start supplier replication
monitoring.
2. If the e-mail address is incorrect, choose Delete. Change the e-mail
address in the procurement system and replicate the supplier master data again.
3. If the supplier master data was not created via supplier registration, select New Business Partner. Change the e-mail address in the
procurement system and replicate the supplier again.
Still if you are unable to replicate the vendors then let us know.
Thanks
Ravi

Purchase order text in material is replicated from ECC to SRM?

Hello experts,
In the standard process of replicating materials from an SAP ECC system to SRM, is the purchase order text tab in MM03 replicated to SRM?
I've tried searcing for this text in SRM but I guess it is not replicated.
Is there a way to do this?
Regards,

hi,
Generally speaking, product longtexts are not automatically replicated to SRM via MW.
The filters of text headers and text lines are not taken into consideration.
-- In case in transaction R3AC1 object MATERIAL has inactive filters for tables STXH and STXL, please remove flags and synchronize the filters.
-- In the backend table CRMOBJTAB still shows inactive entries for both tables.
-- Check the notes no. 555520 and 839995. Please apply and follow the instructions given in the longtext.
Now the filters should work and the basic longtext should get replicated.
thanks,
Ashwin
Do reward points for useful suggestions

SEND PR data from ECC to SRM using PI

Hi PI Guru's
Please advise if there is any documentation to send the PR's from ECC to SRM using PI.
If not PRs in general if need to exchange any documents from ECC6.0 to/from SRM using PI.
Can we use ABAP proxys or IDOCs.
Any help would be greatly appreciated.
Rgds
Nikki

decide proxy or IDOC or RFC based on the business requirement, first search any std IDOc or RFc available if not then go for proxies.
chirag

How to get G/L account and cost centres from ECC to SRM...

Dear All,
How to get G/L account and cost centres from ECC to SRM...
Please let me know the steps...
Thanks
Ravi

Hi
GL account - You can define in SPRO- Cross application settings--Account assignment ->Define GL account for product category and account assignment category.
or you can use BADI BBP_DETERMINE_ACCT.
In Organisation Strucute - You can Map the backend cost center via KNT cost center attribute .
Regards
Muthu

ECC TO SRM-MDM CATALOG THROUGH SAP PI

We have a scenario where we are sending data from ECC to SRM-MDM Catalog through SAP PI and data is coming from ECC through proxy and sending to SRM u2013MDM catlog through file adapter. In ESR part we have used SAP defined standard service interfaces (CatalogueUpdateNotification as sender interface and MDMInfoRecordDataTransmission as a receiver interface). The mapping used is also standard one.
Now we have got requirement to send the data for vendor mat no, manufacturer field of info records from ECC to SRM-MDM catlog. But we are unable to find out these two fields in standard interfaces/messages. Can anybody guide us how to add these fields in the current data types or is there any other standard interfaces we can use.
Thanks in advance.

Hi Shiv,
Many thanks for your reply.
Since we're not using XI / PI scenario and this is an upgrade from SRM 5.5 to SRM 7, Iu2019m using the same approach that was already used in SRM 5.5 with CCM 2.0.
The idea is that the catalogue and all the records maintained need to be associated to a contract. So, I add the contract ID and the correspondent contract item in the import file, in addition to the supplier name, product ID, price information and so on. I mapped the contract ID with the field contract price.
In relation to the price information fields, as I want it to be visible for any user that accesses the product catalogue, I tried different approaches:
1.Using OCI Price information u2013 amount, currency, price base quantity and price base quantity UoM;
2.Using OCI Price contract u2013 amount, currency, price base quantity and price base quantity UoM;
The first approach didnu2019t work very well, as I was not able to see price information when accessing the catalogue. I could only see it once I transfer the items to the SC. In addition, this approach had one problem. The products were displayed but it was not possible to select the items one by one. To do that I needed to select all the items of the catalogue and after that the detail of the contract ID was displayed in every item, allowing me to choose the items that I want to select to my SC.
The second approach was better as the information was visible when accessing the SC and I was able to select all the items, one by one, as it should be. The main problem of this approach was that Iu2019m getting errors in the SC when the materials have stock u2013 u201CInterface data contains errorsu201D. Or alternatively, if the items didnu2019t have stock, the SC was possible, but when I tried to create a PO from that SC, It simply does not work.
So, can someone help me? Any ideas?
Thanks in advance.
Best regards,
Andreia

PO Changes from ECC to SRM 7.0 using PurchaseOrderChangedInformation_Out

Hello,
I am having an issue with sending PO changes made in ECC to SRM. When a PO is changed in ECC, I see an XML message with the sender interface name of PurchaseOrderChangedInformation_Out in namespace http://sap.com/xi/APPL/Global2 being created in ECC in SXI_MONITOR.
However this fails in XI because there is no configuration (receiver determination) in XI to handle this sender interface. I have setup the SAP supplied SE_Services_Procurement scenario in XI.
We are on XI 7.0 and SRM 7.0
Has anyone faced this issue before ? Are PO changes handled through PurchaseOrderChangedInformation_Out ? For PO creates I see a PurchaseOrderERPRequest_Out_V1 message being created in ECC and this is indeed transferred to SRM
Thanks
Anil

Dear Anil,
About SRM7.0 and XI please see url:http://esoadocu.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?packageid=DE4157EA06BD7BF1A3C7001A64D3F462&id=C66D0901602211DA36BB000F20DAC9EF

How is the integration with ECC in SRM 7.0??

Hi,
Working with SRM 5.0 or 5.5 the use of XI for integration with ECC is not mandatory because when we send any document from ECC to SRM like requisitions (to convert them in shopping cards) or when we send any document from SRM to ECC like shopping cards, PO´s, contracts, we only use the RFC´s and the abap programs.
Is the same behavior with SRM 7.0?????
Could the integration from SRM 7 with ECC 6 work with RFC´S without XI or for this vertions is XI mandatory?????
Thanks

SRM70 is closely integrated with XI for transferring docs between ECC and SRM. SAP introduces eSOA tech nology with SRM70 and hence all documents like PR from ECC to SRM, Central Contract from SRM to ECC, PO creation (Classic), etc uses this techn ology.
Thanks,
Jagadish

Transfer Data from ECC to SRM

Hi ,
I'm trying to transfer data from ECC to SRM for creating bid document ( Function : BBP_PD_BID_CREATE ). After transferring the data I want to get the data back to ECC ( I need bid document number to write on delivery document's field ). What's the best way to do this ?
Regards.

Hi vinit ,
I've written code to call 'BBP_PD_BID_CREATE' in ECC. But ECC and SRM have different structures. So i am not sure how i can define data to send SRM.
Here is my code in ECC program
CALL FUNCTION 'BBP_PD_BID_CREATE' IN BACKGROUND TASK
   DESTINATION 'XXX'
   IMPORTING
     I_REF_GUID    =
     I_BAPIMODE    =
     I_PARK        =
     I_SAVE        =
     I_TESTRUN     =
     I_HEADER      = I_HEADER ?
     IT_ATTACH     =
     IT_DYN_ATTR   =
     IT_CONDITIONS =
    EXPORTING
      E_HEADER      = E_HEADER ?
      ET_ATTACH     =
      ET_DYN_ATTR   =
      ET_CONDITIONS =
    TABLES
       I_ITEM        =
       I_PARTNER     =
       I_LONGTEXT    =
       I_SDLN        =
       I_ORGDATA     =
       I_HCF         =
       I_ICF         =
       I_TOL         =
       I_WEIGHT      =
       IT_EXCHRATE   =
       E_ITEM        =
       E_PARTNER     =
       E_LONGTEXT    =
       E_SDLN        =
       E_ORGDATA     =
       E_HCF         =
       E_ICF         =

Transfer of PR from ECC to SRM

Hi experts,
I am new to SRM & my questions can be bit easy. We have implemented PDP & while transferring the PR from ECC to SRM, the PR got stuck in sxmb_moni in SRM. Now when i see the error /sappo/ppo2 it shows "cannot save template: Insert Items".
I have checked the Org. Structure and i think the attributes defined to the RFC_USER is also correct because i can create the shopping cart without an error from this user.
So please help me.
Thanks & Regards
Himanshu singh phartyal

Hi,
Would you please apply note 1821480 and retest the issue with a new PR?
Regards,
Ivy

Modify vendor number when replicating vendor master data from ECC to SRM

Hi,
Is there a way to modify vendor number(manually input vendor number e.g. from a file) when replicating vendor master data from ECC to SRM using the vendor master data user exit (SAPMF02K)?
Does anyone have documentation on the user exit, how do I use it??
Thanks and Regards'
David

Hi David,
Please go through the link below:
[Enhancement SAPMF02K Vendor Master Data - question about LIFNR;
Regards
Anirban

ECC -- PI -- SRM via proxies

Similar Messages

Maybe you are looking for