IDOCs not syndicating to ECC 6.0

Hi Guysl,
Hope you all are good!
Currently I am working on SAP NW MDM 7.1, Material and Vendor master, I have SAP portal through which users creates materials as well as Vendor to be created it in the MDM and created materials and vendors will send to ECC 6.0. This complete process takes place in following way.
User>raise request on Portal>comes for Approval>Approved materials gets created in MDM>IDOCS get created in ECC>remains in MDM ready folder(for some unknown reason)>need to do mynute changes on the record-->material gets created in the ECC.
I will more clear on the above scenario now, we implemented MDM in Automobile industry, so material duplications happens on the large scale. so After above process MDM creates only basic view of material and rest of the views such as finance, sales related views as per their requirements.
Now, the system is completely ready and functioning smooth except one major problem, where materials are getting created though portal, it comes to MDM, necessary checks are happening and material gets created into the ECC system, but...
There are materials which approves through portal, comes into MDM but not reflecting into the ECC system, it happens only for some materials which is similar as materials which approves and goes to the ECC system, there is some syndication level problem..
Any suggestion would be appreciated.

Hi Mandeep
Material locked by itself
As per my understanding, there is nothing wrong in your code, Splitting the message in XI etc will also not help.
I mean you will get this error while posting the IDOC in ECC if that time that record is being edited by some user of ECC.
Make sure that the Materials which you are updating through IDOC posting that time these materials should not be edited by any user of ECC else you will get this error.
See, if the material is locked by some other user error message will also point out which user has locked the data which is not the case here-->Material locked by itself If the Idoc fails due to parallel processing/edit of same material by other user it will have status as 51.
Also the Idoc has been posted succesfully here, status 53, but it has not updated the material tables.
Sometimes Idocs have 64 status- ready to be transferred to application but are not processed, due to issues like loop in the FM, load/volume which can be reviewed for resolution.
@Swapnil- Suggest you to contact ECC ABAP consultant on this.
hope this helps.
Best regards- Ravi

Similar Messages

ADDR_GROUP is somehow not syndicated to ECC

Hi all,
I set up a scenario containing MDM 7.1, PI 7.1 EHP 1 and three ECC 6.0 systems that handles a customer master data flow. The direction from ECC -> PI -> MDM works fine so far (DEBMDM). The Syndication part (MDM -> PI -> ECC) is great (MDM Adapter is cool!) in terms of updating already existing data in ECC. However when it comes to centrally creation of customer data in MDM then the problem is that the record is not created in ECC. Sending to ECC works but I can see that in ECC the ADDR_GROUP field is empty (I have set it to BP in syndicator ). When I debug in WE19 ( FM: MAP2I_BAPIAD1VL_TO_ADDR1_VAL ) the following statement is not set:
MOVE BAPIAD1VL-ADDR_GROUP
TO ADDR1_VAL-ADDR_GROUP.
This is the reason why in WE02 I get the error message: 'Status: Application document not posted - Pleas specify an address group'. In case I set it to BP during debugging the idoc is processed correctly and the customer created. I am using the standard export map DEBMDM06_R3.
My question is as simple as straight forward: why is the ADDR_GROUP field not sent to ECC although I have set a default value for this in syndicator? The setup in PI should be ok as well.
Thanks!
BR,
Erdal.

Hi Erdal,
ADDR_GROUP is part of the E1BPAD1VL segment. Please check the other elements of this segement: is there any field mapped? OR do you use static values only? If the latter one is the case, you're running into a common trap of the Syndicator. You need at least one mapped field so that Syndicator creates the segment... As a workarround I'd suggest the following: Clone the Language keys of the Customer record. Map it to the LANGU_CREA element of E1BPAD1VL. This should ensure the creation of the complete segment.
Best regards
Michael

Idoc not appearing in Xi system

Hi experts,
I have developed a idoc to file scnario but the idoc trgerred in the ECC system i snot comming to XI. I have done all the setting IDX1 and IDX2 and partner profile settings in ECC. the idoc status is 03 in ECC which says the idoc is sent to port successfully, but it is not appearing in SXMB_MONI in XI. It used to work earlier. Is there any batch job or peogram does this transfer. what do i check?/
thanks
sankar

Hi,
Add the Logical System of SAP R/3 in Integration Directory as shown in the Blog and check Now
The specified item was not found.
And also check these Disscussions
No service for system in Integration Directory
No Service for System XYZ,Client 300 in Integartion Directory
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 7, 2008 8:16 AM

G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

i am getting the dump.
the fuction module is not presend in ECC 5.0
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          04/05/2007 07:13:25
ShrtText
Function module "G_G_IDOC_REC_ZZINCOT" not found.
What happened?
The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be
    found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPLGUIF" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
     termination messages, especially those beyond their normal deletion
    date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
     was neither
caught nor passed along using a RAISING clause, in the procedure
     "IDOC_INPUT_GLROLL" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The program "SAPLGUIF" contains a CALL FUNCTION statement. The name
    of the function module to be called is "G_G_IDOC_REC_ZZINCOT".
No function module exists with the name "G_G_IDOC_REC_ZZINCOT".
    All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
       to upper/lower case and underscores ("_")
    b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
       may not have been activated (ABAP Dictionary)
       may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
    Is the program "SAPLGUIF" currently being changed?
    If an enqueue/dequeue module is involved, is the activation
    of the lock object missing in the ABAP/4 Dictionary?
You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC
    "SAPLGUIF" or "LGUIFU05"
    "IDOC_INPUT_GLROLL"
Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":
G_G_IDOC_REC_COFIT
G_G_IDOC_REC_FILCT
G_G_IDOC_REC_ECMCT
G_G_IDOC_REC_GLPCT
G_G_IDOC_REC_GLT0
G_G_IDOC_REC_SECURE
G_POSTING_ZZINCOT
G_G_IDOC_SEND_COFIT
G_G_IDOC_SEND_ECMCT
G_G_IDOC_SEND_SECURE
If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
     "IDOC_INPUT_GLROLL"
"(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "d48ix100"
    Network address.......... "151.162.153.62"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C65EFD4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 2
    Short dump setting....... "full"
Database server.......... "d48ix100"
    Database type............ "ORACLE"
    Database name............ "D48"
    Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
    Created on............... "Nov 5 2006 20:46:58"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
Patch level.............. "156"
    Patch text............... " "
Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
    Roll..................... 16128
    EM....................... 8379856
    Heap..................... 0
    Page..................... 16384
    MM Used.................. 2530176
    MM Free.................. 1657232
    SAP Release.............. "640"
User and Transaction
Client.............. 010
    User................ "OS0730"
    Language key........ "E"
    Transaction......... "YICUPLD "
    Program............. "SAPLGUIF"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".
    The main program was "Y21091IRECON ".
The termination occurred in line 65 of the source code of the (Include)
     program "LGUIFU05"
of the source code of program "LGUIFU05" (when calling the editor 650).
    Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
     occurred in the
procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not
     declared in the
RAISING clause of the procedure.
    The procedure is in the program "SAPLGUIF ". Its source code starts in line 5
    of the (Include) program "LGUIF$05 ".
Source Code Extract
Line SourceCde
35
36 *Prüfen, ob Customizing richtig eingestellt ist
   37     CHECK EXIT IS INITIAL.
   38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.
   39
40 *Für Einzelposten neue Belegnummern vergeben
   41     CHECK EXIT IS INITIAL.
   42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER
   43                                       IDOC_CONTRL-MESTYP.
   44
45 *Füllen der Segmentdaten
   46     CHECK EXIT IS INITIAL.
   47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.
   48
49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.
   50       IDOC_SEGMENT = IDOC_DATA.
   51       APPEND IDOC_SEGMENT.
   52     ENDLOOP.
53
54 *Name des zu rufenden Funktionsbausteines ermitteln
   55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.
   56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.
   57
58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen
   59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB
   60     IF NOT E1GLTTF-TAB30 IS INITIAL.
   61       L_TAB30 = E1GLTTF-TAB30.
   62     ELSE.
63       L_TAB30 = E1GLTTF-TAB.
   64     ENDIF.
>>>>>     CALL FUNCTION ROL_FUNCNAME
   66          EXPORTING
   67               MESTYP             = IDOC_CONTRL-MESTYP
   68               DOCNUM             = IDOC_NUMBER
   69               TAB                = L_TAB30
   70          TABLES
71               IDOC_SEGMENT       = IDOC_SEGMENT
   72               IDOC_STATUS        = IDOC_STATUS
   73               RETURN_VARIABLES   = RETURN_VARIABLES.
   74
75   ENDLOOP.
76
77 *Keine IDOC's empfangen
   78   IF SY-SUBRC NE 0.
   79     RAISE WF_ERROR_PROCESS.
   80   ELSE.
81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind
   82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'
   83                            OR MSGTY = 'E'.
   84       EXIT.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 2
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY                                                                           &

I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

Data not reflecting in ECC

We have cycle of material or vendor creation as given below.
New vendor/material creation on portal > Approve on portal > Check in MDM data manager > PI > Check ECC > Table Entry.
In many cases we have found Materials or vendors are reflecting in MDM after approval from portal but not going in ECC.
In some cases we have observed that PI_MDM sender adapter is picking up same file twice. The data contain payload are same in both messages.
While posting these messages in ECC 1st Idoc is successful in WE05 & 2nd is throwing error u201Cvendor is locked by user ABC (our own user ID)u201D
MDM adapter in PI server is occasionally picking same XML twice from MDM ready folder & tries to post both Idocs in ECC at same time, hence at ECC system gives an error.
Kindly suggest the solution.
Regards,
GAG

Please have a look at the Note 947081, Now on a broader level
this can be achieved by the Note mentioned above.
the hierarchy of what locale a component will be shown in the portal,
will be :
1)component- if he have a locale define
2) portal mandatory locale -
3)user locale
4)browser locale
5)Portal default locale
6) system locale
if you check on the prtDefault.properties file you will see
a line with : request.defaultcountry=us . on the hierarchy it is No 5.
on your Portal it determine to 'us', so you can make the change on this
level to uk , that way the default locale will take effect only if
the locale was not determine on a higher level.
and for your question : that way
afrench user will have a french locale. because the user locale locate
on a higher level on the hierarchy.
Hope the information will help you.

IDocs have disappeared between ECC and PI

Hi All,
A couple of days ago 3 idocs went missing between ECC and PI.
That day 293 idocs of the same message type were sent to the same partner through PI. In PI we only found 290. The 3 IDocs were sent in the same second in the early afternoon. All IDocs before and after were processed correctly.
The IDocs are unknown in IDX5 and in Runtime Workbench on PI.
The idocs were not in SM58.
I found them in WE05, with the correct status. The status update from status = 01 to 30 to 03 took place in the same second.
25 seconds later, new IDocs of the same message type were created and processed successfully by PI.
At the time the idocs disappeared there were no problems with either ECC or PI, as far as we know.
The interface is live for more than 2 years. In the meantime no changes have taken place.
I have read the links below
Finding missing IDocs
Interface Troubleshooting Basics
It's a mystery to me. Where have those idocs gone?
Anybody any idea?
Kind Regards
Edmond Paulussen

Hi Edmond,
On the SAP PI system have a look in transaction IDX5. Take the IDoc number that you could not find in PI and search them in IDX5.
If you cannot find those IDoc in IDX5 then they never reached PI.
Regards,
Jannus Botha

Idoc WPUWBW: Status 51 - IDoc not fully processed

Hi All!
Hi All!
This is regarding Goods Moment.
In Quality, Idoc is successfully generated at POSDM system and also in ECC system.
In Production, Idoc is successfully generated at POSDM, but in ECC it is failed (Idoc WPUWBW: Status 51-IDoc not fully processed).
So, at WPER it is showing as In deficit of stock. But stock is available.
Kindly suggest me how to close this issue.
Note: PFA Below. Its the screenshot of the error at WPER.
With Regards,
Yarnagula Sudhir.

Dear Venu
Difficult to answer with this limited information. If you share some more info will be easier to help
regards
Manish

Confirmation was not replicated in ECC

Hi All,
I am new to SRM.
Requisitioner created confirmation for the PO. In ECC, If I went to transaction ME23N, entered the PO and confirmation does not show up under PO History as it should. Confirmation was not replicated in ECC.
Please suggest me the way to resolve this.Could youn please suggest me the related BADI name also.
Thanks & Regards
Sai

Hi Sai,
can you check your confirmation status in SRM ?
It should be "approved". Otherwise check your WF customizing.
Then an IDOC is sent to R/3. If not check your ALE customizing.
You should check in R/3 if the IDOC MBGMCR is created (transaction WE05 or BD87), and what is its processing status.
If the IDOC processing failed in R/3, then you won't have anything in R/3 PO history, normal, but also an error message is raised in SRM application monitors, saying that IDOC n° XXX could not be processed successfully.
Rgds
Christophe
PS: please reward points for helpfull answers

IDOC not there in WE02

Hi Gurus,
I am doing a FILE TO IDOC scenario for taking Material Master data from the MDM system and posting the IDOC into the R/3 system..
The entry is there in MONI with the chequred flag but there is no IDOC in we02 of the R/3 system.
Also , i pasted the payload from teh MONI and checked in the mapping and the test was shown to be successful.
Can Anyone please tell me what can be the cause and its probable solution?
Thanks in advance,
Shweta.

(1) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
The problem is in Technical routing.
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
(2) Error Scenario - ATTRIBUTE_IDOC_METADATA
Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
(3) Error Scenario - IDOC not yet created in target SAP R/3 system.
Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is u2018"Partner profile not configured" check point 9.
Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.
(4) Error Scenario - Partner profile not configured.
Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.
regards
chandra

IDOC not displayed in WE05

Hi Experts,
I have successfully run my scenario CSV-pi-Idoc yesterday. IN MOni XML file is Ok. In R/3side (WE05) Idoc generated successfully. But Yesterday night Basis people change R/3 password. Now my problem is in R/3 IDOC not displayed in WE02.
Iam also change password in SM59. But no result. Where can I do changes. can any one help me.
Thanks
Hari

Hi Hari,
Make sure in SXMB_MONI in your PI system the message is showing successful flag in outbound side (ie.. drag the scroll bar to ur right had side and see if you can see checkered flag). If you see any error then go to tcode sm58 (trfc queue) and filter based on dates and u will find error logs in detail and take appropriate action.
Mostly it might be authetication problem so better to check in ur R/3 destination in Sm59 in PI system if your rfc test and authentication test is successfully showing green or not.
Thanks,
Prasanthi.

Idoc Not received?

Hi
During data loading , I got one Error that Idoc Not received.
What will be the cause of problem and How to resolve it?
Regards & Thanks
Durai

Hi Robert Negro !
I checked , Dump has been there.
How can I resolve?
what will be other causes apart from the Dump?
Thanks A Lot .
Regards
Durai

CRM To ECC Sold to party Communication Details Not populated in ECC

Hi All
i have one problem when we create sales order through crmd_order we need to give sold to party and ship to party numbers suppose like
8000002166 for both and status i keep as order created and in partner tab i i seem all partner funtions(sold to, ship to ,bill to, payer)with 8000002166
in header overivew i given posting date as feature date like 30-09-2013 then i try to save this order.
the order generated sucussfully but problem is i am not getting sold to party details in ECC when i check VA03 And open cretaed order in CRM and clicking on sold to party and i seem details for this but i am not getting communication details like telephone number and email id extension number.
for this sold to party we already maintained all communication details in CRM.When i open this sold to party BP i am able to see all details
didnt understand why these details not replicated to ECC?
We implemented one custom class there we implemented badi.
IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
i am not getting BAPI ADDRESS Table values into CT_BAPIADDR1
how can i send communciation details to ECC For sold to party?
The code part we follow like below
TYPES : BEGIN OF t_otc,                                                        " Type to create a table with the given columns.
          bpid            TYPE bu_partner,                                       " variable of store processed business partner ID's
          otcid           TYPE bu_partner,                                       " variable of store processed OTC ID's
          otcguid         TYPE bu_partner_guid,                                  " variable of store processed OTC GUID's
          address         TYPE bapibus1006_address,
          tel1_numbr      TYPE ad_tlnmbr1,
          tel1_ext        TYPE ad_tlxtns1,
          e_mail          TYPE ad_smtpadr,
          END OF t_otc.
*&                             V A R I A B L E S                         &*
DATA : lv_bp_payer      TYPE bu_partner,                                       " Variable To Cast the payer Id into BU_Partner data type.
         lv_partner_fct   TYPE crmt_partner_fct,                                 " Variable To Store Partner Function Number.
         lv_partner       TYPE bu_partner,                                       " Variable To Store Current Business Partner ID.
         lv_process_type TYPE crmt_process_type,                                " Variable to Store process type.
         lv_sales_org     TYPE crmt_sales_org,                                   " Variable to store sales org. name of order
         lv_dis_channel   TYPE crmt_distribution_channel,                        " Variable to store distribution channel of order.
         lv_division      TYPE crmt_division,                                    " Variable to store division of sales org. data.
         lv_role          TYPE comt_partner_parvw,                               " Variable to store retrieved role from FM.
         lv_role_value    TYPE parvw,                                            " Variable to store the role value of Partner Functions.
         lv_otc_guid      TYPE bu_partner_guid,                                  " Variable to store OTC GUIDs for the OTC ID.
         lv_otc_id        TYPE kunnr.                                            " Varaible to OTC ID revocered from Table.
DATA: lv_busspartner           TYPE bapibus1006_head-bpartner,
        lw_central_data          TYPE bapibus1006_central,
        lw_centraldata_person    TYPE bapibus1006_central_person.
*&                             W O R K A R E A S                         &*
DATA : lw_address       TYPE bapibus1006_address,                              " Work Area to store address recovered for BPID.
*Start of code change for Defect 904 Fix
         lw_tel           TYPE bapiadtel,
         lw_email         TYPE bapiadsmtp.
*End of code change for Defect 904 Fix
*&                          INTERNAL TABLES                              &*
DATA : li_otc           TYPE TABLE OF t_otc,                                   " Internal Table to Store the OTC IDs and BPS.
         li_values        TYPE          zconst_values_t,
*Start of code change for Defect 904 Fix
         li_tel           TYPE STANDARD TABLE OF bapiadtel,
         li_email         TYPE STANDARD TABLE OF bapiadsmtp.
*End of code change for Defect 904 Fix
*                       F I E L D - S Y M B O L S                         *
FIELD-SYMBOLS: <f_orderadm>      TYPE bad_orderadm_h_mess,
                 <f_otc>           TYPE t_otc,                                   " Field-Symbol to Read the OTC TABLE data.
                 <f_partner>      TYPE bad_partner_mess,                        " Field-Symbol of Partner Table For Looping.
                 <f_bapiparnr3>    TYPE bapiparnr3,                              " Field-Symbol to Store The Row of BAPIPARNR3.
                 <f_bapiaddr1>     TYPE bapiaddr1,
                 <f_orgman>        TYPE bad_orgman_mess,                         " Field-Symbol to Read the ORGMAN table.
                 <f_values>        TYPE zcr_const_values.
*&                             C O N S T A N T S                         &*
CONSTANTS : lc_program_name     TYPE progname      VALUE 'ZOTC',
               lc_param_payer      TYPE paramname     VALUE 'PAYER',              " Constant to Store Payer Parameter name.
               lc_ref_kind         TYPE crmt_object_kind VALUE 'A',
               lc_req_1            TYPE zrequest_no VALUE '1',
               lc_req_2            TYPE zrequest_no VALUE '2'.
* Retrieving the general and Common Data for a Order.
READ TABLE it_bus_trans_msg-orderadm_h INDEX 1 ASSIGNING <f_orderadm>.
IF sy-subrc EQ 0.
    lv_process_type = <f_orderadm>-process_type.
ENDIF.
* Reading the Orgnisation Details from ORGMAN Table.
READ TABLE it_bus_trans_msg-orgman WITH KEY ref_kind = lc_ref_kind ASSIGNING <f_orgman>.
IF sy-subrc EQ 0.
*   Storing the Sales Organisational Data to find the OTC_ID.
    lv_sales_org = <f_orgman>-sales_org.
    lv_dis_channel = <f_orgman>-dis_channel.
    lv_division = <f_orgman>-division.
ENDIF.
* Retrieving the partner function number for the payer by giving requirement no 2 and rule no 1.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
    EXPORTING
      pi_program_name = lc_program_name
      pi_req_no       = lc_req_2
    IMPORTING
      po_const_values = li_values.
IF sy-subrc <> 0.
    RETURN.
ENDIF.
* Reading the value for the constant with the name as PAYER.
READ TABLE li_values WITH KEY param_name = lc_param_payer ASSIGNING <f_values>.
IF sy-subrc NE 0.
    RETURN.
ENDIF.
* Retrieving the Partner ID for the PAYER.
READ TABLE it_bus_trans_msg-partner ASSIGNING <f_partner> WITH KEY ref_partner_fct = <f_values>-constant_value.
IF sy-subrc EQ 0.
*   Storing the current partner ID.
    lv_bp_payer = <f_partner>-ref_partner_no.
ENDIF.
REFRESH li_values.
* Retrieving the Partner Function Number which are to be checked for replacing with the OTC ID with request no 1 and rule no 01.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
    EXPORTING
      pi_program_name = lc_program_name
      pi_req_no       = lc_req_1
    IMPORTING
      po_const_values = li_values.
IF sy-subrc <> 0.
    RETURN.
ENDIF.
* Transferring the constant value to our table for Partner Fucntion.
LOOP AT li_values ASSIGNING <f_values>.
* Read Partner table for Header data and the reference partner function retrieved.
    READ TABLE it_bus_trans_msg-partner WITH KEY ref_kind = lc_ref_kind ref_partner_fct = <f_values>-constant_value ASSIGNING <f_partner>.
    IF sy-subrc EQ 0.
*     Storing Current Partner Function.
      lv_partner_fct = <f_partner>-ref_partner_fct.
*     Storing Current Partner No.
      lv_partner = <f_partner>-ref_partner_no.
*     Retrieving the Partner Role (R/3) for the current partner function of CRM.
      CALL FUNCTION

The problem is in the Lotus Notes security level, not in SAP.

Table M_VMVLB does not exist in ECC 5.0

Hi,
We found that table M_VMVLB is available in 4.6C system but not available in ECC 5.0.
Do yo have ay idea about this? Is there any other table created for this ?
Regards,
Umesh

Hi Umesh,
as such kind of match code tables like M_VMVLB are not longer supported by the ABAP basis, all these match code tables where replaced by normal data base tables, e.g. the content of M_VMVLB can be found in table SHP_IDX_PICK now.
General information about the changes in match codes of delivery processing can be found at the release info for 4.70 - component LE-SHP-DL.
Regards; Ulrich

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Limit PO price changes are not replicated to ECC backend

Hi all,
SRM 5.0 ECS SP13.
When I change the value(increase/decrease) in limt PO which is already created(PO is changed for first time) and order the PO,under Overview screen.,the PO total value(at header level) shows the correct changed /new value while at the Item level,the Net price is shown as the old value!However when I go and check the item details,the field "VALUE" and "EXPECTED VALUE" have the changed/new value.
Because of the above issue,the PO changes are not replicated to ECC backend system.When I tested the BAPI BAPI_PO_CHANGE1 with the test data,there is no error mesasge in ECC backend system.
After this,when I change the PO for second time(again value increase/descrease),the total value and net price is shown correctly in SRM and changes are also replicated to ECC backend system!
I have also checked the cong for SPOOLPARAMETERS under Set Control Parameters and eveything is set correctly as shown below
SPOOL_JOB_USER     User that execueds spool job.     CUA_ADMIN
SPOOL_LEAD_INTERVAL     intervall by which the retrytime incr.     60
SPOOL_MAX_RETRY     Max. number of retrys for writing BAPIS     10
Can someone throw some pointers how to resolve the above issue.
Thanks in advance.

Hi
can you recreate the same issue
are you saying that
1. create a limit po for 100 USD and replicated to ECC AS 100 USD total value.
2 . now update the PO in SRM 150 USD and it was not replicated to ECC ?
or
1. limit sc
2. Limit PO
3. update not reached ECC.
Note 1284361 - Limits not transferred to backend purchase order
Symptom
Extended classic scenario.
You have ordered a purchase order with more than one hierarchy item containing a limit.The purchase order is created or updated in the backend system without errors but the limits are missing in the backend purchase order.

IDOCs not syndicating to ECC 6.0

Similar Messages

Maybe you are looking for