Outbound CREMDM

Hi
I'm trying to send Vendor master using CREMDM but I dont know how to push data out of R3 system, it doesnt show up in bd14, there is only CREMAS but I wanna use CREMDM, any idea?
Thanks

Hi Hikmet
Use MDM_CLNT_EXTR.BD14 will give separate IDoc for different vendors and using this we get single IDOc for group of Vendors.
Also follow this link on how to use  MDM_CLNT_EXTR.
Background job requirement  in Systems like MDM
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50260ae5-5589-2910-4791-fc091d9bf797
Award if useful
regards
Ravi

Similar Messages

  • Create vendor in ERP R/3 with internal number range

    HI,
    When I create a new vendor from MDM in R/3 with internal number range ADRMAS is processed OK but CREMDM is in status 51 because of missing address data.
    According to sap note  1052964 (se below) ADRMAS must be the first IDOC and it should contain the vendor number, but this is not possible with internal number range. How do you overcome this problem and how do I get the vendor number back to MDM?
    ALE inbound needs the customer / vendor account number within the ADRMAS IDoc to link the ADRMAS IDoc to the follwing DEBMAS / CREMAS IDoc correctly. Therefore field <OBJ_ID> in ADRMAS segment <E1ADRMAS> must contain exactly the same value as fields <KUNNR> / <LIFNR> in the corresponding DEBMAS / CREMAS IDoc. If this value is not provided, the Business Address Service stores the address but is unable to link the address later on to the corresponding Customer / Vendor.
    Kind regards
    Jonna

    We have worked around these problems in the past.  These are the steps we took:
    1.  We created a custom program to process a CREMDM IDOC.  This custom program was pretty simple.  It called the function module to process a CREMAS IDOC (IDOC_INPUT_CREDITOR) then did a committ.  The program captured the vendor number and then called the function module (IDOC_INPUT_ADRMAS) that processes an ADRMAS IDOC (It plugged in the previously captured Vendor number in the ADRMAS).
    2.  Using this custom program, it is not necessary in PI to split the CREMDM into a CREMAS and an ADRMAS.
    3.   The last step in the custom program kicked off transaction MDMV to trigger an outbound CREMDM IDOC back to MDM.  This was necessary to update the vendor number in MDM. 
    Tom Belcher

  • CREMDM how to trigger it

    Hi,
    i´ve been trying to trigger CREMDM message as outbound message for vendors to connect with the syndicator, but although i´ve set up the distribution model, created the partner profiles, no idoc is generated when i create or change a vendor. How can i trigger this message?

    Hi,
    You need to add the message type CREMDM in Partner Profile (Tcode we20) as Outbound parameters and IDoc Type CREMDM04.
    And, you need add the message type in Distribution Model View (Tcode BD64) in Sender Logical system and Outbound Message type (CREMDM).
    If you are pleased with this help, rate the help.
    Sincerely,
    Bala

  • FI Invoices Outbound - Any Standard Program ?

    Hi,
      Is there any Standard program to send SAP FI Open, Chnaged and Closed Invoices in to a File (Outbound)?
    How to Track Invoice is new or chnaged or closed ?
    I appricate any help. Thank you.

    i am away from my system...Just check BKPF / BSEG tables...U can get the field name....
    Award points if useful...

  • How to compare delivery date in schedule lines and PGI in outbound delivery

    Hi,
    I want to create a report to monitor and compare different dates in sales and delivery process.
    One of my key figure is the comparison between date confirmed to the customer, that I can find in the schedule line of the sales order, and the actual goods issue date from the outbound delivery.
    But I can't succeed in making the link between delivery and schedule lines, means between LIKP and VBEP.
    Would you have any idea?
    Thank you.

    It seems there's no exact (table) connection / link between delivery item and schedule line item.
    Those who were searching for this thing (link / connection between delivery item and schedule line) were recommended to use FM "RV_SCHEDULE_CHECK_DELIVERIES".
    This FM calculates the delivered quantity for each schedule line, so it makes link between the delivery item and schedule lines - however if you check the code it's quite sophisticated...
    (if you put a breakpoint in the FM and display a SO in VA03, you can check how the parameters have to be populated with data).
    Schedule Line and Delivery Link
    Edited by: Csaba Szommer on Aug 5, 2011 12:03 AM

  • Getting error while testing a outbound file in oracle B2B11g

    Hi,
    I am trying to configuare a outbound scenario in oracle B2B 11g.
    I have created .ecs file and .xsd file and created a document type also and i am using generic file 1.0 as a lintening channel protocol and trying to read the input xml document from a perticular path.
    I had setup partner and agreement also. everything is working fine and also file is succesfully polling from the source folder but i am getting error in B2B as :
    B2B-50083
    Error Description Machine Info: (infva0325) Description: Document protocol identification error.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Document protocol identification error.
    Can anyone guide me how to resolve this error?
    I had tried everything but of no use.
    Please do reply me with your suggestions.

    Hi Anuj,
    Please find below xml data which will be saved as .txt file for outbound processing. Let me know if there are any changes i have to do. Please let me know if you need any further information. Listening channel is reading the file but in agreement level it is failing.
    <?xml version="1.0" encoding="UTF-8"?><Transaction-DESADV XDataVersion="1.0" Standard="EDIFACT" Version="D93A" CreatedBy="ECXEngine_837" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" CreatedDate="2011-12-14T12:59:40" GUID="{2d323135-3336-3630-3232-313938393033}" xmlns="urn:oracle:integration:b2b:099C29D4C4ED419194917C20ADF8ABC3">
    <Internal-Properties>
    <Data-Structure Name="Interchange">
    <Property Name="InterchangeSenderID">senderID</Property>
    <Property Name="InterchangeSenderQual">senderQuali</Property>
    <Property Name="InterchangeReceiverID">RecieverID</Property>
    <Property Name="InterchangeReceiverQual">RecieverQuali</Property>
    <Property Name="RepeatingSeparator"/>
    <Property Name="InterchangeApplicationRef">DESADV</Property>
    <Data-Structure Name="Transaction">
    <Property Name="TransactionID">DESADV</Property>
    <Property Name="TransactionControllingAgency"/>
    <Property Name="TransactionMessageVersionNumber">D</Property>
    <Property Name="TransactionMessageReleaseNumber">93A</Property>
    <Property Name="TransactionAssociationAssignedCode"/>
    </Data-Structure>
    </Data-Structure>
    </Internal-Properties>
    <Segment-UNH>
    <Element-0062>#ControlNumber#</Element-0062>
    <Composite-S009>
    <Element-0065>DESADV</Element-0065>
    <Element-0052>D</Element-0052>
    <Element-0054>93A</Element-0054>
    <Element-0051>UN</Element-0051>
    <Element-0057>EDIT30</Element-0057>
    </Composite-S009>
    </Segment-UNH>
    <Segment-BGM>
    <Composite-C002>
    <Element-1001>351</Element-1001>
    </Composite-C002>
    <Element-1004>3364382</Element-1004>
    </Segment-BGM>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>137</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    <Loop-Group_2>
    <Segment-NAD>
    <Element-3035>SH</Element-3035>
    <Composite-C082>
    <Element-3039>7393142020009</Element-3039>
    <Element-1131 xsi:nil="true"/>
    <Element-3055>9</Element-3055>
    </Composite-C082>
    </Segment-NAD>
    </Loop-Group_2>
    <Loop-Group_2>
    <Segment-NAD>
    <Element-3035>CN</Element-3035>
    <Composite-C082>
    <Element-3039>7350056030012</Element-3039>
    <Element-1131 xsi:nil="true"/>
    <Element-3055>9</Element-3055>
    </Composite-C082>
    </Segment-NAD>
    </Loop-Group_2>
    <Loop-Group_10>
    <Segment-CPS>
    <Element-7164>1</Element-7164>
    </Segment-CPS>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>1</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>210587</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>3</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>1</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>2</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>210510</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>3</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>1</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>3</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>081349</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>1</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>2</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>NB</Element-1153>
    <Element-1154>JF074</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>21E</Element-2005>
    <Element-2380>20160905</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>4</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>051596</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>1</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>2</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>NB</Element-1153>
    <Element-1154>116812505</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>21E</Element-2005>
    <Element-2380>20150131</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    </Loop-Group_10>
    <Segment-CNT>
    <Composite-C270>
    <Element-6069>2</Element-6069>
    <Element-6066>4</Element-6066>
    </Composite-C270>
    </Segment-CNT>
    <Segment-UNT>
    <Element-0074>#SegmentCount#</Element-0074>
    <Element-0062>#ControlNumber#</Element-0062>
    </Segment-UNT>
    </Transaction-DESADV>

  • Intrastat - Inbound/Outbound of non valuated materials used in production.

    Hello everyone,
    I've found several threads and very useful posts (ex: Re: PO Creation of free goods for intrastat reporting)  regarding similar issue, but the solution proposed was manual input, therefore not answering totally to my client requirement.
    I am actually performing maintenance activities and there is this new business process, I have been searching for the correct understandind of this process regarding intrastat here and I haven't found.
    So i will describe the process hoping that someone can give me some hint:
    Vendor A
    Customer B
    Raw Material R
    Finish Product P
    Service S
    1. So we ( Vendor A ) receive raw material from our Customer B (+mov.type +)
    2. We ( Vendor A ) with a production order process the Raw material R into Finish Product P.
    3. We ( vendor A ) send the Finish Product P back to the Customer B.
    4. We ( Vendor A ) then issue an invoice for the Service S to the Customer B.
    5. It can occur that we Vendor A, can send back the Raw material R which was not manufactured back to Customer B (with a mov type.)
    So thiswas the scenario and how the process is beeing done, and the client understanding is:
    - As far as i understood, (please correct me if i am wrong) the Raw Material R must be declared (Quantity and statistic value) in Purchasing Intrastat, in the transactions where the Vendor A receives the raw material and as well in the case that they send it back to Customer B.
    - Regarding the Invoice from the Vendor A to Customer B, the Raw Material R is incorporated in the Finish Product P, therefore I've been told that, the Statistic Value determined in the invoice in this situation has to include the cost value of the raw materials R.
    My issues in MM are the following:
    1 - If Raw Material R is non valuated, how can i maintain its statistic value to be declared, in inbound as well outbound? as an Info-record?
    My issues in SD are the following:
    1 - If the Statistic Value GRWR can be for example 102% calculated over the net value, and if the cost value of Raw Materials R are to be included, so i would have to add them somehow to the statistic value.
    In this case the question comes up, where do i maintain the value of the raw materials R, and how to add it to the statistic value automatically ?
    Regarding what is implemented in this client, they have SD intrastat running, but not MM intrastat was implemented.
    Feedback would be highly appreciated!!
    Thank you in advance.

    Hi Sergio,
    I have this exact same requirement but on a bigger scale.
    The complexities are:
    1. The raw material which client use, that can be either supplied by customer or can be procured by client. Remember, customer's raw material and my externally procured raw material is exactly same in all properties.
    2. There are many customers who send same exact raw material.
    Requirements:
    1. Client wants to use same material codes (for raw materials and even for finished products) for normal production cycle and for Job work cycle. Master data needs to be the same, and data need to be separated at transaction level.
    2. Whatever raw material client gets from customer, its statistical value should be entered at the time of goods receipt.
    Please suggest if preference processing can handle this.
    Thanks & Regards,
    Vishal

  • Goods Receipt of HU in an Outbound Delivery not updating HUMSEG and Hu Hist

    Hi,
       I have a pecuiliar prob ...  I am trying to do GR (MIGO) for an Outbound Dely containing HU (non HU Stor Locn), although I am able to post the article documnet. The Gr article doc doesnt get updated in the table HUMSEG and in the HU History.
       Whereas if I do the Gr for an Inbound Delivery containing HU  in the same stor location , the article docs gets updated in HUMSEG.
        Can anyone throw some light on this?
    REgards,
    BG

    HI Csaba,
       Now I am trying to create GR for Inbound Dely containing the HU through MIGO and not VL32n , it is throwing the error
    Packing can only be updated via inbound delivery dialog
    Message no. VLA311
        We are into ECC 6.0 and it seems that SAP NOte 1384533 has already been implemented , but still I dont see the VLA 311 message in System Messages under the Logistic Execution path of SPRO.
       I have been reading the SAP Note 199703, but when I set the GR Assignment field of the Conf Control to blank and remove the movt type for Dely Item Cat ELN , it doesnt allow me to create HU in the Inb Dely, although it allows me to create a GR for the Inbound Dely through MIGO .
         Can you please help me in overcoming the prob.
    REgards,
    Binayak
    Edited by: Binayak Ghosh on Jun 15, 2011 4:37 PM

  • Need BAPI for MIGO to create a Goods Receipt against PO &Outbound Delivery

    Hi Friends,
    GRN’s (Good receipt notifications) created in DHL (Non SAP system) will need to be communicated to SAP.
    I need to post goods receipt using input data in MIGO. Is there any BAPI that i can use.The requirement is like below:
    PO number field in output file is checked against entries in EKKO-EBELN, if a match is found the GR is posted against a Purchase Order otherwise LIKP-VBELN is checked and if a match is found GR is posted against an Outbound Delivery.
              If PO Number = EKKO-EBELN    GR against Purchase Order
                            = LIKP-VBELN      GR against Outbound Delivery
    Based on the above condition I need to create a Goods Receipt. 
    Could you please tell me the GM code, movement types and the required fields to be passed for the BAPI?
    The fields available are with us are...
    Header text. - Bill of Lading- Posting Date-Quantity- UOM--- Vendor Batch / Batch / Serial No --- PO Number or Delivery Number… SLED
    Are these fields sufficient for doing MIGO with the BAPI or do we require more fields???
    Please provide sample code if possible.
    Waiting for replies,
    Thanks and Regards,
    Sudha

    Hi Friends,
    GRN’s (Good receipt notifications) created in DHL (Non SAP system) will need to be communicated to SAP.
    I need to post goods receipt using input data in MIGO. Is there any BAPI that i can use.The requirement is like below:
    PO number field in output file is checked against entries in EKKO-EBELN, if a match is found the GR is posted against a Purchase Order otherwise LIKP-VBELN is checked and if a match is found GR is posted against an Outbound Delivery.
              If PO Number = EKKO-EBELN    GR against Purchase Order
                            = LIKP-VBELN      GR against Outbound Delivery
    Based on the above condition I need to create a Goods Receipt. 
    Could you please tell me the GM code, movement types and the required fields to be passed for the BAPI?
    The fields available are with us are...
    Header text. - Bill of Lading- Posting Date-Quantity- UOM--- Vendor Batch / Batch / Serial No --- PO Number or Delivery Number… SLED
    Are these fields sufficient for doing MIGO with the BAPI or do we require more fields???
    Please provide sample code if possible.
    Waiting for replies,
    Thanks and Regards,
    Sudha

  • Goods Receive for Outbound Delivery Without Reference using MIGO

    Dear Colleague ...
    We might need your insight on the case below related to Goods Receive of Outbound Delivery without Reference using MIGO:
    (1) In the current SAP Enjoy screen of MIGO, we are allowed to select the reference document (e.g. = PO, Material Document, Inbound Document, Outbound Document, etc.)
    (2) We did 3 (three) kind of test set: GR for Inbound Delivery, GR for Outbound Delivery with STO and GR for Outbound Delivery without reference.
    (3) The first 2 (two) cases work just find with MIGO.  We believe it is because the receiving plant is pretty much determined in the reference document, which is PO (case 1) or STO (case 3)
    (4) However, the last case came up with the error message "Goods receipt not possible for delivery 8000610236: error code 5".  We believe that this is the standard design of SAP, that the receiving plant is required and it is not defined explicitly in the delivery document.
    (5) Moreover, we also believe that that's the reason why SAP (via the Logistic Execution module) provide the Handling Unit and Shipment, which can be used to perform such receive function, which will imply the MM posting (goods issue and goods receive) IF there is stock transfer involved.
    Appreciate for any thoughts or input on the above.  Many thanks,
    Alvon Sibarani

    use transaction mb0a it will work for the scenario.

  • Help needed on Outbound Goods Receipt (IDoc)...

    Hi Experts,
      Can we use the message type WMMBXY and IDoc type WMMBID02 for Outbound Goods Receipts scenario also (Sending Goods Receipts information to target system).
      Because WMMBID02 seems to be for Inbound going by the documentation in WE60. Can we use this for outbound as well? All the field mapping is perfect with respect to this IDoc and all the required fields exist in this IDoc.
       I am struggling to find a suitable outbound process code and processing function module to trigger Idoc from MIGO Transaction once the goods receipt is created / generated.
      Please advice me on how to achieve the above functionality.
    Thanks in Advance.

    Hi,
    check with this link it might be helpful to u ...
    <u>Purchase Order
    Re: Problem to send idoc for a Good Receipt created
    https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=1279261</u>
    Hope this will surely help u ...
    regards,
    sana.
    reward for useful answers...

  • CPALookupException Couldn't retrieve outbound binding

    Hi gurus,
    We're working on our test environment and we have a strange error:
    com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI
    protocol handler. Failed to determine a receiver agreement for the
    given message. Root cause:
    com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't
    retrieve outbound binding for the given P/S/A values:
    FP=;TP=;FS=BS_XIT_IT_ADYCLNT100;TS=BS_XIT_IT_INCAS_VALDOBBIADENE;AN=MI_AnagrArticoli_IN;ANS=http://goldenlady.it/it/Incas/I03/AnagrArticoli001
    The receiver agreement and the other objects in the scenario exist and
    work properly in the development scenario, while in the test system we
    have this error. Looking at the cache of the test XI system we can see
    all the configuration objects, also the receiver agreements that we
    need.
    We have already refreshed all the caches and also restarted the java
    instance but the problem still remains...
    By the way, we noticed a strange behaviour because the log files about
    this errors are written not in the folder that refers to the test
    system (XIT) but in the one that refers to the development system
    (XID). Could this be a problem connected to our errors?
    We suppose that the adapter frameworks looks in the wrong CPACache (the development instead of the test one).
    Points rewards good answers
    Mattia

    Hi,
    Please do the following it will solve the problem:
    Prerequisites:
    check the correctness of configuration of your scenario at your end.
    Please do the following:
    1) Check destination INTEGRATION_DIRECTORY_HMI in SM59. Does it returns a HTTP status of 500 with reqid not found. It means RFC is working fine.
    2) http://xihostname:port/CPACache/refresh?mode=full  
    with PIAFUSER and check whether it shows the correct output or not. Extremely important: check whether the authorization error is there or not for services users.
    3) Check the services in SAP XI in visual admin
    4) Reimport of SAP Basis content is done properly or not.
    5) If possible try to restart the J2EE server.
    6) Also check the inconsistency of SLD using SAP note no:
    764176
    Hope it will solve your problem.
    Thanks & Regards
    Prabhat

  • Middleware problem -Outbound queue is stuck in SAP R/3 system with message

    Hi Middleware gurus ,
    We are stuck with a serious issue . We are trying to download Business partners from SAP R/3 4.6c system to SAP CRM 5.2 system using CRM Middleware
    Previously we did a successful Initial download of 2 Business partners from SAP R/3 to CRM . Their BP numbers in CRM are 001 and 002 . The Delta load is working fine for the both the BPs which are already downloaded
    Now , the real problem is when we are trying to download a new Business partner . When we set the Filter ( BP no 003 ) in MW adaptor object CUSTOMER_MAIN and start the Initial load again , we see that the Outbound queue is getting stuck with message “STOP” .
    There are two queues generated in SAP R/3 system with names “MASS_CRM_CUSTOME” and “R3AD_CUSTOME” . The status for both the queues is “STOP” and when go for details it mentions “sapsuck ..SAPMSSY1 “ -Message no. SR 053.
    Even we checked the txn SMW01, the Bdocs message is "Recived ( Intermediate state) " for Bdoc type BUPA_MAIN.
    We really don’t as to why the Initial load worked fine with 2 BPs  and later when want to do more BP Initial Load the Outbound queue is getting stuck
    Also , by unlocking the 2nd queue “R3AD_CUSTOME” we are able to release it , but the first queue “MASS_CRM_CUSTOME*” is stuck
    Please help us urgently
    Regards
    Dinesh and Ritvij
    Email : [email protected]
    Mobile -+91=9704933315

    Hi Praveen and other Middleware gurus,
    We checked on this . Actually the RFC is used for connecting to SAP R/3 system.
    We also raised an OSS message on this and found a reply that in transaction CRMM_BUPA_MAP, we can map the required BP . But the SAP support guy recived an error received the error:
    An RFC link is not maintained in the Middleware
    Message no. CRM_BUPA_MAPPING051
    We have set the RFC link , but still the problem continues!!!
    Please help further..
    Regards
    Dinesh and Ritvij

  • CDR by Outbound Dialed Number

    Hello,
    Is it possible to run a report on an outbound dialed number? I have been tasked to find how many times a number has been called. I normally did this with query analyzer with an if statement in older versions of CM but this is on UCM 8.
    Any help is greatly appreciated. 
    Thank you to all in advance.

    What version are you on?
    Mine shows "By User/Phone Number/SIP URL" for the first option.
    You can try using the "By User Extension" option but it may not work.
    You can use the CDR->Export CDR function to just export that date range to an Excel sheet and do your filtering there.
    The SQL queries would be another option as well.
    Brian

  • Stoarage location is not being reflected in the outbound delivery

    Hi
    I have a scenario of creating outbound delivery with respect to sales order, But when i am creating outbound delivery vai  tranaction Vl10H , The system creates outbuond delivery but the stoarge location is not being reflected in the outbound delivery  . Since this storage location is WM managed  hence the WM  status shows that the transfer order is not required .
    When i tried to put manually the storage location  the system  throws an error that this storage location in not maintained in plant R001 .
    Althoght the stoack has been there in the stoarage location with resepct to plant ans also  the matrerial master is also been extended for  this storage  laocation and all the respective views such as WM and Sales hasbeen maintianed .
    Could any one guide me what correction is to be done to incorporate the Storage location in Delivery ?
    Thnaks and Regards
    RAJ K

    Hi,
    did you check if there is a storage location determination maintained for the relevant combination of shipping point, plant and
    stor.conditions (table TVKOL)?
    Please also check if the storage location determination is activated for the relevant delivery item type in customizing (transaction 0vlp - field "Determine storage location" (V_TVLP-BELGO)).
    Regards,
    Ely

Maybe you are looking for