Dele PO in SRM 4.00

Hi,
we are trying to develop a program that can delete PO items in SRM and R3, we are excecuting the FM BBP_PD_PO_DB_DELETE_MULTI in the following way:
l_otd-guid = '479D144AA4FB3608E10000000A021B2A'.
append l_otd.
CALL FUNCTION 'BBP_PD_PO_DB_DELETE_MULTI'
EXPORTING
    IV_SAVE_ON_DB                  = 'X'
TABLES
    it_objects_to_delete                 = l_otd
    ET_DELETED_OBJECTS         = l_delted
    et_messages                          = l_messg
after running this program the PO Item is not deleted
do I need to execute another thing ?
may be some commit function or any thing else to complete the delete ?
Tanks in advance

ok, I've found th way to do that
Just follow the next squence of FM
BBP_PD_PO_UPDATE
BBP_PD_PO_SAVE
BBP_PROCDOC_RESET_BUFFER
BBP_PD_PO_STATUS_CHANGE_WF
commit work and wait.

Similar Messages

How to del all info regarding source of supply from R3 reqs coming to SRM

Hello Experts,
We are trasfering requisitions from ECC to SRM.
By standard functionality, if a requisition comes with a source of supply assigned to it, and this requisition is sent to SRM, we have configured that a Shopping cart that has a SOS assigned should create an automatic PO.
However, these requisitions might have materials that already have a local contract in SRM. This is colliding with the SOS assigned previously in the Preq in ECC.
Is there a way to wipe out the SOS information from the requisitions coming from ECC?
Thanks!
Regards,
Gilberto Gallardo

Hi. You could try BBP_SOS_BADI.
Alternatively, why not disable the souce of supply fields in ECC using field selection config?
That way users could not enter a source of supply in ECC.
Regards,
Dave.

Help ! SRM 4.0 - Was (dispatcher) doesn't start =(

Hi everyone,
I'm trying to do a fresh install of SAP SRM 4.0 (Wintel, SQL), at this moment I'm installing the WAS.
The installation process was fine, but I'm having problems doing the post-processing activities (start / stop the server).
Any clue about this ?
I appreciate a lot your help !!!!
Regards from Mexico,
Diego
pd: this is the dispatcher log:
trc file: "dev_disp", trc level: 1, release: "640"
Mon Jun 06 13:13:58 2005
kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
length of sys_adm_ext is 312 bytes
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 43
intno 20020600
make: multithreaded, ASCII
pid 2888
***LOG Q00=> DpSapEnvInit, DPStart (00 2888) [dpxxdisp.c 1100]
 shared lib "dw_xml.dll" version 43 successfully loaded
 shared lib "dw_xtc.dll" version 43 successfully loaded
 shared lib "dw_stl.dll" version 43 successfully loaded
 shared lib "dw_gui.dll" version 43 successfully loaded
Mon Jun 06 13:14:03 2005
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3886]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: JAVA is not active
DpShMCreate: sizeof(wp_adm) 6624 (828)
DpShMCreate: sizeof(tm_adm) 2219848 (11044)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(vmc_adm) 0 (320)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 05720040, size: 2505416)
DpShMCreate: allocated sys_adm at 05720040
DpShMCreate: allocated wp_adm at 057217A8
DpShMCreate: allocated tm_adm_list at 05723188
DpShMCreate: allocated tm_adm at 057231B0
DpShMCreate: allocated wp_ca_adm at 059410F8
DpShMCreate: allocated appc_ca_adm at 05945748
DpShMCreate: allocated comm_adm_list at 05946EB8
DpShMCreate: allocated comm_adm at 05946ED0
DpShMCreate: allocated vmc_adm_list at 05975CD0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 05975CF8
DpShMCreate: allocated wall_adm at 05975D00
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 1131 blocks reserved for free list.
ES initialized.
Mon Jun 06 13:14:04 2005
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( GIMDEVWB01) [dpxxdisp.c 9736]
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 43
Release check o.K.
Mon Jun 06 13:14:44 2005
ERROR => W0 (pid 3172) died [dpxxdisp.c 12187]
ERROR => W1 (pid 3180) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W2 (pid 3188) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W3 (pid 3196) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W4 (pid 3204) died [dpxxdisp.c 12187]
ERROR => W5 (pid 3212) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W6 (pid 3220) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W7 (pid 3228) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
killing W0-3172 (SIGUSR2)
ERROR => DpWpKill(3172, SIGUSR2) failed [dpxxtool.c 2468]
killing W1-3180 (SIGUSR2)
ERROR => DpWpKill(3180, SIGUSR2) failed [dpxxtool.c 2468]
killing W2-3188 (SIGUSR2)
ERROR => DpWpKill(3188, SIGUSR2) failed [dpxxtool.c 2468]
killing W3-3196 (SIGUSR2)
ERROR => DpWpKill(3196, SIGUSR2) failed [dpxxtool.c 2468]
killing W4-3204 (SIGUSR2)
ERROR => DpWpKill(3204, SIGUSR2) failed [dpxxtool.c 2468]
killing W5-3212 (SIGUSR2)
ERROR => DpWpKill(3212, SIGUSR2) failed [dpxxtool.c 2468]
killing W6-3220 (SIGUSR2)
ERROR => DpWpKill(3220, SIGUSR2) failed [dpxxtool.c 2468]
killing W7-3228 (SIGUSR2)
ERROR => DpWpKill(3228, SIGUSR2) failed [dpxxtool.c 2468]
NiWait: sleep (10000 msecs) ...
NiISelect: timeout 10000 ms
NiISelect: maximum fd=421
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Jun 06 13:14:54 2005
NiISelect: TIMEOUT occured (10000 ms)
dump system status
Workprocess Table (long) Mon Jun 06 18:14:54 2005
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 3172 Ended no 1 0 0
1 DIA 3180 Ended no 1 0 0
2 UPD 3188 Ended no 1 0 0
3 ENQ 3196 Ended no 1 0 0
4 BTC 3204 Ended no 1 0 0
5 BTC 3212 Ended no 1 0 0
6 SPO 3220 Ended no 1 0 0
7 UP2 3228 Ended no 1 0 0
Dispatcher Queue Statistics Mon Jun 06 18:14:54 2005
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
3
2000
10
10
--------++++--
+
DIA
6
6
2000
6
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id 14
wake_evt_udp_now 0
wake events total 9, udp 8 ( 88%), shm 1 ( 11%)
since last update total 9, udp 8 ( 88%), shm 1 ( 11%)
Dump of tm_adm structure: Mon Jun 06 18:14:54 2005
=========================
Term uid man user term lastop mod wp ta a/i (modes)
RM-T8, U9, , diegohernande, 13:14:22, M0, W-1, , 1/0
Workprocess Comm. Area Blocks Mon Jun 06 18:14:54 2005
=============================
Slots: 300, Used: 2, Max: 1
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
1
DISPATCHER
-1
WPCAAD001
NiWait: sleep (5000 msecs) ...
NiISelect: timeout 5000 ms
NiISelect: maximum fd=421
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Jun 06 13:14:59 2005
NiISelect: TIMEOUT occured (5000 ms)
Shutdown server ...
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes...
Stop gateway
killing process (3152) (SOFT_KILL)
Stop icman
killing process (3164) (SOFT_KILL)
Terminate gui connections
send SHUTDOWN to REM TM 8
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/300/8
LOCK WP ca_blk 2
return errno (-17) to T8
errormsg without overhead: take mode 0
NiBufIAlloc: malloc NiBufadm, to 0 bytes
try to send 14 to M0
NiBufSend starting
NiIWrite: write 14, 1 packs, MESG_IO, hdl 7, data complete
REL WP ca_blk 2
set status of T8 to TM_DISCONNECTED
NiSelClear: removed hdl 7 from selectset
DpDelSocketInfo: del info for socket 7 (type=3)
NiBufClose: clear extensions for hdl 7
NiBufSetStat: bufstat of hdl 7 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 7 / socket 252
dp_tm_adm[8].stat = DP_SLOT_FREE
DpGetSchedule: next schedule 1118081704
DpGetSchedule: no schedule found
DpITmSlotRelease: release slot 8
DpListInsert: insert elem 8 into tmadm_free_list (at begin)
DpListInsert: 193 elems in tmadm_free_list
DpListRemove: remove elem 8 from tmadm_inuse_list
DpListRemove: 8 elems in tmadm_inuse_list
[DpProcDied] Process lives (PID:3152 HANDLE:404)
waiting for termination of gateway
NiWait: sleep (1000 msecs) ...
NiISelect: timeout 1000 ms
NiISelect: maximum fd=421
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Jun 06 13:15:00 2005
NiISelect: TIMEOUT occured (1000 ms)
[DpProcDied] Process died (PID:3152 HANDLE:404)
[DpProcDied] Process died (PID:3164 HANDLE:396)
DpHalt: cancel all lcom connections
MPI CancelAll 2 -> 0
MPI DeleteAll 2 -> 0
NiIMyHostName: hostname = 'GIMDEVWB01'
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 163 bytes
NiBufSend starting
NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 9962]
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiSelClear: removed hdl 3 from selectset
MBUF state OFF
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/300/8
LOCK WP ca_blk 2
make DISP owner of wp_ca_blk 2
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 20)
MBUF component DOWN
NiBufClose: clear extensions for hdl 3
NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 3 / socket 324
MsIDetach: detach MS-system
EsCleanup ....
***LOG Q05=> DpHalt, DPStop ( 2888) [dpxxdisp.c 8495]
Good Bye .....

Hi Diego,
i have a question.
i know that we need SRM 4.0 installation on WAS and ITS to be installed.
my question to you is....
do we need to install EBP separately if we have already installed SRM 4.0 ( in other words is EBP part of SRM 4.0 installation or is it separate)
and for ITS i am running WAS 6.4 and i know that ITS is an integral part of it so how do we activate ITS for SRM 4.0
Thanks a lot in advance
Harish

Deleted PO's in SRM

Hi SRM Gurus,
We have some local Purchase Orders which was deleted for some reason.
Where can I see those deleted PO's.
Can anyone help me out?
Reg.,
Sridhar.
[email protected]

Sri,
Create a report which receives the PO number (object_id), call the FM BBP_PD_PO_GETDETAIL using that parameter, then:
Try the FM BBP_PD_PO_STATUS_CHANGE for each position, with the following params:
I_GUID                   -> PO header guid
IV_ITEM_GUID        -> PO item guid (each position)
I_ACTIVITY             -> 'DELE'
I_SAVE_DB            -> 'X' to save changes, ' ' to not save them
I_TEST_RUN           -> 'X' to test, ' ' to commit
At last, if you don't have any error messages and the i_save_db is 'X', exec the COMMIT WORK to post changes in DB.
Hope this can help you.
Regards,
Gerardo.
Please reward points for useful answers.

BAPI_PO_CREATE1 : missing del indicator on a service line

Hello gurus,
I'm facing a problem in the first distribution of a Purchase order (created from a Purchase Requisition) from SRM. The problem occours only if the PO has been created from a PR taken from the sourcing cockpit in SRM and happens only on a specific system/backend.
The problem is that a service line marked as deleted in SRM is transferred WITHOUT the deletion flag; in other systems I can test on, the outline is correctly transferred with the deletion indicator (ESSL-del = 'X').
Seemed a problem that could be easily investigated in debug; however, I tried a bit without success by tracing a parallel debug on a "correct" system; I can advice a difference only after a "perform get_current_data", that is to say, last step of the BAPI, when the creation process of the PO has already been done (and just await a commit).
In order to realize at which point and why the deletion flag on the service line is removed, I tried to investigate the class CL_PO_ITEM_HANDLE_MM; it contains an interface, IF_SERVICES_MM, which offers just three methods: GET_DATA, SET_DATA and GET_SRV_DATA. I expected to find a setter method for service data, but I was wrong.
The SET_DATA method is used once during BAPI_PO_CREATE1 execution and passes parameters concerning the ITEM position (im_comsrv) and acconting-related data (lt_acc_tab), so I didn't understand where the PO object in the BAPI is updated with service items data. That should be an useful starting point in order to backtrack and solve the problem; I guess that something goes wrong when the PO position is related to the corresponding PR position, but no idea about how to identify that point on the code.
Any clue or suggestion will be highly appreciated
ps: obviously, data passed at BAPI_PO_CREATE1 are identical for both the "OK" system and the "KO" one. Tried also to analize the stack trace by using SE30, but the call sequences are really complex and not easy to compare. A nice-to-have feature could be to track the entire code executed, row by row, on each system, but I guess it's a task impossible to manage.
Edited by: Matteo Montalto on Jun 17, 2010 4:31 PM

you can either share your code and your source file to have the people check if the error is on your part or you can directly contact SAP if you are the opinion that it is an error in their BAPI code.
But without looking at code and source file it is not possible to do any evaluation except you are looking for clairvoyants

PO text not updated on SRM portal

Hi Friends,
We have upgraded SRM 4.0 (SRM server 5 SP04) to SRM 5.0 (SRM server 5.5 SP03) in MM-SUS scenario using XI 3.0.
In a standard functionality text at header and item level of PO is visible on the portal. However currently we are not able to see text in the "Messages from purchaser" textedit box on the portal.
We have checked in the R/3 idoc. Following two segments carry this information:
IDOC Segment ON R/3 for header text: E1EDKT2
IDOC Segment ON R/3 for ITEM text: E1EDPT2
All the content of these segments are also there in the XML on SUS, but are not visible on the portal.
For example, following are the contents displayed in the text box:
Vendor :DS063D -SHARDA MOTOR INDUSTRIES LTD
Buyer :SANT GANESH
Validity Start Date :21.03.2006 & Validity-End Date:31.03.2099
Payment Term :D022 --19 days from date of receipt
Incoterms :Free del.to stores-Frgt.paid --
Similar is the problem for item text.
I will be very grateful if anybody can suggest the settings missing or program correction required on SRM in BSP application (SRMSUS).
Regards,
Prashant Rahane

Hello Rajesh,
Few more pointers, if works:
1. Check the roles, sometimes security restricts role by document types.
2. Extended classic scenario is activated.
3. As a standard, there are 3 purchasing tabs in SRM 7.0 for buyer depending on portal roles, ECC, SRM & harmonized role (ECC & SRM), Check if you are trying to create PO in SRM/Harmonized role purchasing tab & not in ECC. Easiest way to check is you will have shopping cart POWL visible in SRM purchasing tab.
Hope this helps.
Thanks
Ashutosh

How to reverse/change SRM PO with status "transaction completed"

We use Extended Classic scenario in our company. There is a PO has outstanding G/R balance, but user accidently hit the button "complete"on this PO in SRM , in result the PO has been completed with status "transaction completed". And nothing can be performed on this PO.
G/R balance is out there and now it has financial impact as it blocked the funding thru internal order.
Anyone have idea how we can resolve this problem. Can we reverse/change the PO status? Please note G/R canu2019t be entered in ECC as restricted.
Thanks,
Frieda

I think it was CRM_JEST. But the way to easily select the correct entries:
1. Go to transaction BBP_PD
2. Enter BUS2201 and the order number
3. Double click on the status table, this will take you to SE16 with all the different status for the PO
4. Select the entry to delete
5. Enable debugging by putting /h into the transaction field
6. Double click "CODE" and change this to "DELE"
7. F8 (leave debugging)
8. Click on the delete icon and save.
Done.

SRM-PI-ECC Integration issue

Hey All
There is some issue coming in Central Contact management scenario.
SRM 7.0
ECC 6.0 EHP 4
PI
*below is the error details we get in SXMB_MONI of SRM Sytem* <REMOVED BY MODERATOR>
<?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>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_UNEXPECTED</SAP:Code>
<SAP:P1><></SAP:P1>
<SAP:P2><Fault></SAP:P2>
<SAP:P3 />
<SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>
<SAP:AdditionalText>System expected the element 'Fault'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unexpected XML element <>; <Fault> was expected System expected the element 'Fault'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Narender
Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM

Thanks Buddy.
We have some progress. Now data passed from SRM to PI and now stucked in ECC. The XML file in SXMB_MONI in ECC, shows the staus "Transfer to External Application" and in ECC SMQ2 Queue XBQRCCR4400000066 stucked with status "STOP".
While dubugging the relevant we are getting the error '"COMMNICUTION_FAILURE"
And the Payload .xml file is as below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:TimeSent>2011-03-11T07:14:32Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SS1CLNT200</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ES1CLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>CCR4400000066</SAP:QueueId>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="BS">SS1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="IS">is.01.auvimel00s971</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:33Z" wasRead="false">
<SAP:Engine type="BS">ES1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20110311</SAP:Date>
<SAP:Time>181433</SAP:Time>
<SAP:Host>AUVIMEL00S962</SAP:Host>
<SAP:SystemId>ES1</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>007</SAP:AdapterStatus>
<SAP:User>RFCUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>001</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_RECEIVER</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>RECEIVER</SAP:PipelineIdExternal>
<SAP:PipelineElementId>1DC6B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_INBOUND_PROXY</SAP:PipelineService>
<SAP:QIdInternal>XBQRCCR4400000066</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">SND_CENTR</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">AC1E020C11E44D79CBD9E0A7</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="MSGID">E04BAF35835783F182AD005056A12FA9</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>2929</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>11916</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>2929</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>258</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>57</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.211</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.256</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.257</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.387</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INBOUND_PROXY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.39</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/XI/engine/?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 4580</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = E04BAF35835783F182AD005056A12FA9</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = CCR4400000066</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface PurchasingContractSRMReplicationRequest_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/Global2</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Work Process ID: 2348</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">ROLLBACK WORK requested by application</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:payload-E04BAF31EF9CE7F189DE005056A10467sap.com">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Can anyone suggest what can be issue ?
Thanks
NAP

SRM PO Document date is getting replicated to ECC as Delivery date

Hello SRM experts,
Please guide me on the following issue. We are using extended classic scenario. SRM 7.0
Delivery date is not getting reflected in the ECC delivery date field.
To know whether this is an standard issue ?
Is there any way out to make proper replication to ECC ?
What might be the reason for this ?
SRM PO created with Delivery date "08/07/2014".
But current date(Document date) "01/07/2014" is picked in delivery date
Delivery date is getting reflected in the Statistical delivery date field under Item details --> Delivery schedule tab

When you create a PO , delivery date is calculated by adding planned delivery time from Purchase info record.
The delivery date calculated thus, is defaulted into the PO for del date and st del date.
If you change the delivery date thus defaulted, without making a manual entry in st del date, the date you entered will default to st del date too,
This change will not happen, if you make a manual entry in the st del date field before you change the del date in the po or you output the PO and then change the del date in the PO.
In case you want to change the delivery date in ECC this exit can help :EXIT_SAPMM06E_012
Thanks
Ankit

XI Error when transfering invoice from MM - XI - SRM.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SRM</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = DEV01</Trace>
<Trace level="1" type="Timestamp">2007-11-05T15:02:42Z INDIA</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 472D3D926B8A3FE0E10000000AC83163</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0002</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0002</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface InvoiceRequest_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement/Global</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SRM</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = DEV01</Trace>
<Trace level="1" type="Timestamp">2007-11-05T15:02:42Z INDIA</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o91" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o91">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o90" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>340</PROGID>
<CONTID>3133</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o90">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>340</PROGID>
<CONTID>3369</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Function call failed; could not find the function BBP_PD_SUSIV_GETLIST Programm: SAPLBBP_BD_DRIVER_SAPXML1; Include: LBBP_BD_DRIVER_SAPXML1U20; Line: 63</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Hi,
We have configured the SAP for Plan Driven Procurement. We have SRM 5.5 version installed along with XI 7.0 and MM 4.7.
The scenario is to send the invoice from MM to SUS (SRM) via XI. We have created a ZNAST program to send the invoice from MM to SUS via XI. The invoice is moving from MM to XI and XI to SUS where it fails due to this error.
We have used OOTB scenarios and have not done any customizations as well.

Default date in SC, PO documents in SRM

Hi SRM gurus,
If we create a shopping cart or direct PO the "Required on" date is same as the creation date ( today's date)
How can we achieve 5 days after todays date in SRM ?
i-e., this is config setting or shall we have to use BADI.
If so pl. let us know the configuration setting in SRM.
We are working with SRM server 5.0 and component version 4.0
Best reg.,
Sridhar.
[email protected]

Hi
As Yann told earlier, you need to go for BBP_DOC_CHANGE_BADI and create two new custom implementations. One for BUS2121 (shopping carts) and one for BUS2201 (Purchase orders).
For every line item, you need to add 5 days to the deliverydate field available in the BBP_DOC_CHANGE_BADI at the item level in the table et_item[].
and in the last of the BADI add this line et_item[] = it_item[].
Let me know incase you face any issues.
Related links to refer ->
Note 752868 - SC desired del.date: Change error message to warning message
Note 768091 - Perf period error when error msg changed to warning msg
Re: entering wrong delivery date format in SC item -> popup dialog
Re: PO Changes, PO date
Re: Shopping cart for services
Regards
- Atul

T-codes in SRM

Dear Gurus,
DO any one have the list of T-codes available in SRM 5.0.
Thanks in advance
Rgds
Giirsh Joshi

Here is the comprehensive list.
Hope this helps.
Reward full points if this answers your questions.
Thanks
Ajay
BBP_ACP Analysis Cockpit
BBP_ACP_CREA_CATGORY SM30 for Maintenance of Categori
BBP_ACP_CREATE_TOOLS SM30 for Maintenance of Tools
BBP_ARCH_RESI Define EBP Residence Times
BBP_ATTR_CHECK EBP Organizational Model: Checks
BBP_AUC_SRM_EX Live Auction Return from Applet
BBP_AUCTION BBP Live Auction
BBP_BE_LIST Vendor List
BBP_BGRD_APPROVAL Background Approval
BBP_BID_CHANGE Change Bid Invitation/Auction
BBP_BID_CONVT Convert RFQ to Auction
BBP_BID_DISP Bid Invitation in Display Mode
BBP_BID_EVAL EBP Bid Evaluation
BBP_BID_EXTSO Display Bid Invitation from SOCO
BBP_BID_INV BBP Bid Invitation Cockpit
BBP_BID_WF_APP Approval TA BidInv for Approver
BBP_BID_WF_CRE Approval TA BidInv for Creator
BBP_BID_WF_REV Approval TA BidInv for Reviewer
BBP_BP_BLOCK Locking of a Vendor
BBP_BP_OM_INTEGRATE Integration BP Orgmanagement
BBP_BW_SC2 SB Monitoring Admin (PD)
BBP_BW_SC3 Shopping Carts per Product
BBP_BW_SC4 Shopping Carts per Cost Center
BBP_CALL_ALERT_INBOX Call Alert Inbox
BBP_CCM_TRANSFER Data Transfer to Catalog
BBP_CFOLDER Redirect from cFolders
BBP_CHECK_USERS Check EBP Users
BBP_CLEANER Start Synchronization with Backend
BBP_CND_CHECK Check Conditions Customizing
BBP_CND_CHECK_CUST Check Conditions Customizing
BBP_CONT_ACTION_DEF Define Action Profiles
BBP_CT_SCM_STAGING Staging UI for Schema Import
BBP_CT_STAGING Staging
BBP_CTR_01 Change Vendors in Contracts
BBP_CTR_03 Display Contracts
BBP_CTR_CHANGE Contract in Change Mode
BBP_CTR_DC Contract in Display Mode/Change pos.
BBP_CTR_DISP Contract in Display Mode
BBP_CTR_DISPCG Contract in Display Mode
BBP_CTR_DISPNR Display Contract without Return
BBP_CTR_EXT_PO Display Contract from PO and SOC
BBP_CTR_EXT_WF Display Contract from Workflow
SRMTcodes1 5/17/2007
Page 2
Field2 Field3
BBP_CTR_MAIN Process Contracts
BBP_CTR_MAINCC Process Global Outline Agreement
BBP_CTR_MASS Perform Mass Changes in Contracts
BBP_CTR_MASSCC Perform Mass Changes in Glob.O.Agr.
BBP_CTR_MASSDO Mass Download of Contracts
BBP_CTR_MASSOP bbp_ctr_massop
BBP_CTR_MASSSH Show Workpa. of Mass Change of Ctr
BBP_CTR_MASSUP Mass Upload of Contracts
BBP_CTR_MON Monitor Contract Distribution
BBP_CTR_SEARCC Find Global Outline Agreement
BBP_CTR_WF_APP Branch from Approval Workflow
BBP_CTR_WF_CHG Branch Contract from Change Workflow
BBP_CTR_WF_CRE Goto Approval Workflow for Creator
BBP_CTR_WF_RVW Goto Approval Workflow for Review
BBP_CUS_ACCESS_SEQ EBP: Define Access Sequences
BBP_CUST_CAT Call Structure Maint. of Catalogs
BBP_CUST_DET_ACCT Determine G/L Account by Category
BBP_CUST_DET_LOGSYS Determine Target System by Category
BBP_CUST_LOGSYS Maintenance of the Backend System
BBP_CUST_TARGET_OBJ MMaint. of Objects to Be Generated
BBP_DYN_ATTR_EDIT Maintenance of Dynamic Attributes
BBP_EVAL_SURVEY Survey Cockpit
BBP_GETCD_ITS Display Change Documents
BBP_MON Open the Monitor Display
BBP_MON_SC Monitor Shopping Cart
BBP_MS_ACC_DET_C Multiple Company: Acct for Category
BBP_MS_BE_C Multiple Company:Maintain FI Backend
BBP_MS_MAP_TAX_C Multiple Company: Tax Code
BBP_MS_MSG1_C Message Control
BBP_MS_MSG2_C Multiple Company: Flex. Message XML
BBP_MS_STD_ACC_C MultipleCompany:LocalAcctAssigmtData
BBP_NUM_AUC Number Range Maintenance 'AUC'
BBP_NUM_AVL Number Range Definition 'AVL'
BBP_NUM_BID Bid Invitation Nr Range Maintenance
BBP_NUM_CONF Procure. Confirm. Nr Range Mainten.
BBP_NUM_INV Invoice Number Range Maintenance
BBP_NUM_INVD Number Ranges for Invoice Template
BBP_NUM_PC No.Range Maint. Contrct/Del.Schedule
BBP_NUM_PCO Number Range Maint for NkObj POCONF
BBP_NUM_PO Purchase Order Nr Range Maintenance
BBP_NUM_QUOT Bid Number Range Maintenance
BBP_NUM_SUSASN Number Range Maintenance: 'SUSASN'
SRMTcodes1 5/17/2007
Page 3
Field2 Field3
BBP_NUM_SUSCF Number Ranges Maintenance: 'SUSPO'
BBP_NUM_SUSINV Number Ranges for 'SUSINV'
BBP_NUM_SUSPCO Number Ranges for 'SUSPCO'
BBP_NUM_SUSPO Number Ranges Maintenance: 'SUSPO'
BBPADDREXT Maintain Vendor Address - External
BBPADDRINTC Maintain Addresses for Own Company
BBPADDRINTV Maintain Vendor Address (Internal)
BBPADM_COCKPIT Administrator Monitor Dummy
BBPADM_MONITOR FlowLogic Service BBPADM_MONITOR
BBPAPPL Define EBP Applications
BBPAPPL_DISP Define EBP Applications
BBPAPPL_TRSP Define EBP Applications
BBPAT03 Create User
BBPAT04 Forgotten User ID/Password
BBPAT05 Self ServiceChange
BBPATTRMAINT Maintain Attributes
BBPAVLDISP Display ALV
BBPAVLMAINT AVL Maintenance ( Display / Change )
BBPBC1 XML invoice transfer
BBPBWSC1 SC Analyses for Manager (Old)
BBPBWSP Start Enterprise Buyer Inbox
BBPBWSP_SIMPLE Start Enterprise Buyer Inbox
BBPCACC Maintain Account Assign. Categories
BBPCF01 GR/SE for Vendor
BBPCF02 GR/SE for Desktop User
BBPCF03 Goods Recpt/Serv.for Profession.User
BBPCF04 Confirmation Approval
BBPCF05 Carry Out Review for Confirmation
BBPCF07 External Confirmation Display
BBPCMSG1 Customizing Flexible Message Control
BBPCMSG2 XML Message Control
BBPCTOL Maintain Tolerences
BBPCU04 Set Up Default Workflows
BBPCU05 Link Manager to Org. Structure
BBPCU06 Link Administrator to Org. Structure
BBPCU07 Current Role for User Generation
BBPCU08 Workflow Wizard
BBPDIFF Version Comparison
BBPGETVD Transfer Vendor Master
BBPGLOBAL Transaction for Internet Transaction
BBPHELP Help for Specific Transactions
BBPINSTALLCOUNTRIES Activate country-specific EBP fields
SRMTcodes1 5/17/2007
Page 4
Field2 Field3
BBPINSTALLSZENARIO Installation of CUF Scenarios
BBPIV01 Vendor User Invoice Input
BBPIV02 Desktop User Invoice Input
BBPIV03 Prof. User Invoice Input
BBPIV04 Invoice Approval
BBPIV05 Perform Invoice Review
BBPIV06 Change Incorrect XML Invoice
BBPIV07 External Invoice Display
BBPIV08 External Invoice Display
BBPIV09 Invoice Entry Invoicing Clerk
BBPMAINAPP Startup for Vendor Approval
BBPMAINEXT Process Vendor or Bidder
BBPMAINEXTPERS Ext. Partner: Maintain Own Data
BBPMAININT Process Vendor or Bidder
BBPMAINMANAGER Process own Company (only)
BBPMAINNEW Request Vendor or Bidder
BBPMAINPURCH Process own Purch.Org. View (only)
BBPMONSTART Start the BBP monitors
BBPOR01 Component Planning for Orders
BBPOR02 Postprocessing Orders
BBPPCO_PO Purchase Order Confirmation: Call PO
BBPPCO_WF Purchase Order Confirmation: Call WF
BBPPCO01 PCO: Prof. User
BBPPCO02 Purchase Order Response: Entered By
BBPPO01 Purchaser Cockpit
BBPPS01 Component Planning for Projects
BBPPS02 Postprocessing Projects
BBPQADISP Display QA
BBPQAMAINT Maintain QA (Display/Change)
BBPRP01 Reporting, Data Retrieval from Core
BBPSC01 Shopping Cart - Full Functionality
BBPSC02 Shopping Cart - Wizard
BBPSC03 Shopping Cart - Limited Functions
BBPSC04 Shopping Cart Status
BBPSC05 Public Template (Create)
BBPSC06 Public Template (Change)
BBPSC07 Manager Inbox
BBPSC08 Employee Inbox
BBPSC09 Administrator Cockpit
BBPSC10 Reviewer Inbox
BBPSC11 Shopping Cart Display Item Overview
BBPSC12 Shopping Cart Display Item Details
SRMTcodes1 5/17/2007
Page 5
Field2 Field3
BBPSC13 Change Shopping Cart
BBPSC14 SC Display for Rec. Mangagement
BBPSC15 SC Display for Cfolder
BBPSC16 SC Number of Itm Det. for Cfolder
BBPSC17 SC Number of Itm Det. for Rec. Mgmt
BBPSC18 Request Temporary Staff
BBPSC19 Request External Staff (Change)
BBPSC20 Gener.Shop.Cart Display Item Overv.
BBPSC21 Shop.Cart Displ. ItemDetail Generic
BBPSHOWVD Display vendor data
BBPSOCO01 Sourcing Cockpit
BBPSOCO02 Sourcing Cockpit Search
BBPSR01 Service Entry (Component)
BBPSR02 Entry Sheet Maintenance (Component)
BBPST01 Start EBR Menu
BBPST02 Start EBR Menu
BBPSTART1 FlowLogic Service BBPSTART
BBPSUBSCRIBE Add additional subscriber user data
BBPTRACE Switch on EBP Trace
BBPTRACK Status Tracking: Call Structure
BBPUM01 Employee Master Data
BBPUM02 Self Service
BBPUPDVD Update Vendor Master Record
BBPUSERMAINT Employee Master Data
BBPVE01 Vendor Evaluation
BBPVENDOR BBP Vendor Logon
BBPWEBMON_SEP Monitor in New Window
BBPWEBMONITOR Application Monitor w/o Flow Logic
BBPWEBMONITOR_CTR Application Monitor w/o Flow Logic
BBPWEBMONITOR_QUOT Application Monitor w/o Flow Logic
BBPWI Central Initial Screen WI Execution
BBPWLRA01 Workload Reassignment
O_BBP_USRCUS Maintain BBP flags (HR, manager)
PPOCA_BBP Create Attributes
PPOCV_BBP Create Vendor Groups
PPOMA_BBP Change Attributes
PPOMV_BBP Change Vendor Groups
PPOSA_BBP Display Attributes
PPOSV_BBP Display Vendor Groups

Can we delete the material from SRM ?

Hello,
In ECC, With MM06 & with MM17 we have marked the materials for deletion but can not completely delete it. still client users shop for those materials and
We have the requirement to permanently delete the materials from respective SLOCs so that those deleted materials will not be available at all to requester for shopping.
Archiving is out of scope. Can we delete the materials from SRM also in commpr01 ? or Suggest any other pointers
Thanks & Regards / Pankaj K

Hi Pankaj
Issue during S.cart creation for mtl which are flagged for del at sto locn
as really said, if you delete a material at SL level , srm not validating but SRM validates at Plant level deletion.
Are you in classic oe ECS, However it would have thrown error while creating PO.
How did you delete the material inSRM ?
After you delete a material in SR, what is the status of material ? Is it blocked, Archieved.
BR
Muthu

Procesar Ofertas en SRM

Buenos días,
tenemos una instalación de SRM 7.0.
Cuando entra el usuario proveedor, a pesar de que hay licitaciones publicadas, no las puede ver, ni tiene disponible el enlace "Procesar Ofertas" en la Pestaña "Licitaciones y subastas". ¿Alguien puede ayudarme?.
Muchas gracias

Hola, el error estaba en que el rol del comprador tenia un numero de rol que no le correspondia al centro donde pertenecia Solo se le cambio al correcto y listo, muchas gracias por sus respuestas y ya di unas estrellitas

SRM workflow reinicio

Hola a todos,
Tengo un requisito que es similar a la del ruta
SPRO -> Servidor SRM -> sourcing -> Definir campos en Compras que desencadenan Workflow
Puedo definir qué campos de un carrito de la compra deben dar lugar a un flujo de trabajo de aprobación cuando se editan.
Pero no lo hace para Ordenes de Compra.
La idea es que se inicie el WF nuevamente solo cuando se modifica un campo del pedido.
No estoy seguro de si es posible para PO. Si es así, alguna sugerencia sobre cómo hacer esto.
Gracias,
Edward.

Hi Arun,
First and foremost: did you run SWU3?
This is a crucial starting point for workflow in SRM as it does various automatic customizations regarding SRM-workflow.
You indicate you activated the workflow. Could you detail how?
One of the safest ways is to use the transaction OOCU.
In the tree presented go to:
SRM > SRM-EBP > SRM-EBP-WFL
In this you can both activate the workflow, activate the event-linkage (telling the system that the SAVE-event on a BUS2121 = Shopping Cart should select WS10000060 as a potential workflow). You should be able to check whether everything is setup correctly using SWETYPV (it should list the BUS2121 + event: SAVED linked to WS10000060, with the event-linkage-checkbox marked).
If it still does not work, please let me know.

Dele PO in SRM 4.00

Similar Messages

Maybe you are looking for