Error while creating a credit memo with reference to invoice

HI aLL,
I am facing one issue while creating a credit memo request in VA01 with reference to invoice.
Our project stock is valuated stock.
When we try top copy the error pops up" Valuated project stock not allowed with customer stock." and the line item is not copied in the credit memo.
Diagnosis:The entered wbs manages a valuated project stock,at the same time sales order stock is maintained on sales order line item.this combo is not allowed as different valuation methods within a project is not allowed.
Tarun Kapur

Dear Tarun!
1.Within a project we can get stock only in PROJECT or in SALES ORDER STOCK.....a single material can not be a both place at particular time ..so keep only one
Project Stock or Sales Order Stock..
2.Check DIP PRofile (ODP1) in usage BILLING AND RESULT ANALYSIS -Charectiristic -SDOC TYPE CMR.....are you selecting right document to which you want to copy .....
Rewards Points if usefull
Regards
SMITH

Similar Messages

  • Creating a Credit memo with reference to Billing document

    Hi All,
    I am creating a Credit memo say CM by with reference to a Billing document say B.The Billing document has been created from a Contract say C.
    Now while creating the CM the contract dates need to be copied from C to the contract data screen of CM.
    I have used Copying control Billing Document to Sales Document for achieving this.
    I have edited the VEDA(Contract data) in the routines 302,303,402 etc. but its not reflecting in Contract data of CM screen neither at header level nor item level.
    Please help me in resolving this.
    Replies appreciated.
    Thanks and Regards,
    Blessy

    Dear Rupak,
    Your price / Quantity is copying correctly from Billing means your Copy Control settings are proper.
    Now while creating Credit Memo Request, after you change Quantity you are currently selecting Update & "B" - i.e. Carry out new pricing.
    Here instead of "B" select "A".
    A means - Copy price components and redetermine scales.
    Here the system:
    1. does not determine any new condition types
    2. and only redetermines the scale prices for changed quantities
    I guess this will definitely solve your problem.
    Hope this helps...
    Thanks,
    Jignesh Mehta

  • Error while creating an Credit memo in AR + R12

    Hi All,
    I am trying to create a credit memo in AR, based on the transaction i.e., an invoice of AR.
    But i am not able to create.
    I am encounter the following error
    "Your credit memo transaction can only credit an invoice or a debit memo line
    Failure encountered in AR_CREDIT_MEMO_API_PUB.Create_request call to arw_cmreq_cover.ar_request_cm".
    My code is as follows:
    DECLARE
    l_dummy varchar2(240);
    l_customer_trx_id ra_customer_trx.customer_trx_id%type;
    l_line_credits_flag ra_cm_requests.line_credits_flag%type;
    l_line_amount number;
    l_freight_amount number := 0;
    l_cm_lines_tbl arw_cmreq_cover.cm_line_tbl_type_cover;
    l_cm_reason_code varchar2(150);
    l_comments varchar2(150);
    l_msg_count number := 0;
    l_msg_data varchar2(20000) := null;
    l_return_status varchar2(1);
    l_request_id NUMBER;
    l_batch_source_name varchar2(150) default null;
    cm_trx_id number;
    BEGIN
    fnd_global.apps_initialize(1018094,50559,222,0);
    mo_global.set_policy_context('S',204);
    arp_global.init_global;
    l_customer_trx_id := 549724 ; --527689;
    l_comments := 'Creation of Credit memo';
    l_batch_source_name := 'Invoice';
    l_cm_lines_tbl(1).customer_trx_line_id := 833940;
    l_cm_lines_tbl(1).quantity_credited := -1;
    l_cm_lines_tbl(1).price := 1000.00;
    l_cm_lines_tbl(1).extended_amount := -1000.00;
    l_cm_lines_tbl(2).customer_trx_line_id := 833941;
    l_cm_lines_tbl(2).quantity_credited := -2;
    l_cm_lines_tbl(2).price := 1000.00;
    l_cm_lines_tbl(2).extended_amount := -2000.00;
    AR_CREDIT_MEMO_API_PUB.CREATE_REQUEST(
    P_API_VERSION => 1.0,
    P_INIT_MSG_LIST => FND_API.G_TRUE,
    P_COMMIT => FND_API.G_FALSE,
    P_VALIDATION_LEVEL => FND_API.G_VALID_LEVEL_FULL,
    P_CUSTOMER_TRX_ID => l_customer_trx_id,
    P_LINE_CREDIT_FLAG => 'N',
    P_CM_REASON_CODE => 'DAMAGED PRODUCT',
    P_CM_LINE_TBL => l_cm_lines_tbl,
    P_SKIP_WORKFLOW_FLAG => 'Y',
    P_CREDIT_METHOD_INSTALLMENTS => null,
    P_CREDIT_METHOD_RULES => null,
    P_BATCH_SOURCE_NAME => l_batch_source_name,
    P_ORG_ID => 204,
    X_REQUEST_ID => l_request_id,
    X_RETURN_STATUS => l_return_status,
    X_MSG_COUNT => l_msg_count,
    X_MSG_DATA => l_msg_data);
    FND_MSG_PUB.count_and_get (
    p_encoded => FND_API.g_false,
    p_count => l_msg_count,
    p_data => l_msg_data );
    dbms_output.put_line('Return Status ==> '||l_return_status);
    dbms_output.put_line('Credit Memo request_id ==> '||l_request_id);
    dbms_output.put_line('l_msg_count ==> '||l_msg_count);
    FOR I IN 1..L_MSG_COUNT LOOP
    DBMS_OUTPUT.PUT_LINE(SUBSTR(FND_MSG_PUB.GET(P_MSG_INDEX => I, P_ENCODED => 'F'), 1, 254));
    END LOOP;
    IF l_return_status <> 'S' THEN
    NULL;
    ELSE
    select cm_customer_trx_id
    into cm_trx_id
    from ra_cm_requests_all
    where request_id = l_request_id;
    dbms_output.put_line(' CM trx_id = '|| cm_trx_id );
    END IF;
    EXCEPTION
    WHEN OTHERS THEN
    dbms_output.put_line('exception error!');
    dbms_output.put_line(substr(sqlerrm, 1, 80));
    fnd_message.retrieve(l_dummy);
    dbms_output.put_line(l_dummy);
    END;
    Please advise me where i am wrong .... Thanks in Advance.
    Regards,
    Basha.
    Edited by: zaheer on Aug 1, 2011 8:43 PM

    I am encounter the following error
    "Your credit memo transaction can only credit an invoice or a debit memo line
    Failure encountered in AR_CREDIT_MEMO_API_PUB.Create_request call to arw_cmreq_cover.ar_request_cm".Please see these docs.
    Listing of AutoInvoice Error Messages and Troubleshooting Tips to Resolve each Error [ID 1138254.1]
    Credit Memo Errors During Autoinvoice Process - Invalid reference line attribute value (REFERENCE_LINE_ATTRIBUTE1-15) [ID 405445.1]
    Thanks,
    Hussein

  • How can we create credit memo with reference to INV

    Hi,
    Pls tell how can we post credit memo with reference to Invoice which is posted through SD.
    Is there any use with reference to field in T.Code FB75.
    Thanks in advance,
    Padmaja

    Hi Vijay,
    I could not found any field for Inv. reference in the Payment Tab of T.Code FB75.
    Is there any facility in SAP to create Credit Memo for a particular customer with reference to Invoice. All the details of that Invoice should get updated in the credit memo automatically.
    Thanks in advance,
    Padmaja

  • Create Credit memo with reference to billing in VF01

    Hi all:
    I want to create a credit memo with direct reference to the original billing. Thus the creation of CMR is not required. This is the new feature as of release 4.5a. In SAP system, I've done the configuration for copying control from billing document to billing document, source (F2) target (G2). Copying requirement 027. Pos/neg qty = + and Pricing type = D. I can create a credit memo with reference to a billing now. However, the system allow multiple credit memos. Duplicate credit memo are unwanted in the system.
    How to control the system to avoid duplicate credit memo?
    Thanks and regards,
    Sim

    Hi Mei,
       In t-code "VTFF" under your item category,the field VBRK/VBRP skuldn't be 001.
       Keep them as zero.
       Reward points if it helps.
    Regards
    Karan

  • Error while creating the sales order with billing reference

    hi alll
    i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
    cheers
    shalsa007........

    Dear SAP SD 007
    I can confidently tell that an enhancement or an user exit has been applied in your scenario
    You have to check that
    Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
    Your people has solved the standard problem by enhancement
    Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
    Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
    To solve this only your people have used userexit
    Line items and qty greyed out means definately there is some enhancement or user exit applied
    You have to check that
    Regards
    Raja

  • Credit Memo with reference to Sales Order

    Dear Friends,
    I am trying to configure customization for the new billing document type (Credit Memo) with reference to an existing sales order, and i want the new billing type also to be listed in the billing due list when we create the invoices with transaction VF04.  Can you pl. advise me the parameters that need to be considered importantly in customization.  Or even a document link would be much appreciated.
    Thanks in advance.
    BR,
    KP

    Hi,
    In VF04 you can give different billing type.
    So in that you can also add your newly created billing type to show in the billing due list.
    If you want your sales order should consider your billing document only then do the setting in VOV8.
    If you want to some thing else then please let us know clearly.
    Regards
    Raj.

  • Credit memo with reference to a sales order with reference to a contract?

    Hello All
    Now I created a quantity contract and the customer paid the Amount that means the billing is done then I started creating sales orders with reference to the contract, can I create credit memos with reference to these sales orders?
    Regards
    Jacopo Francois

    Hi,
    You can create a contract for a longer duartion say 1 year, andyou can create sales order in reference to your contract. This would be an ideal scenario in case of service materials.
    You can now surely create credit memo's in reference to this sales order.
    You will invoice the sales order first and create a credit memo request in reference to your sales invoice and then invoice the credit memo request to raise your credit memo for the customer.
    Reward if helpful.
    Regards
    Ravi

  • Posting a Credit Memo with Reference to the Invoice

    Dear all,
    I'd like to post a Credit Memo with Reference to the Invoice but in transaction FB65 or I can't find field to input Reference to the Invoice
    Please tell me where I can Reference to the Invoice
    Thank in advance
    Minh

    Dear all,
    When I create a a Credit Memo (Transaction FB65),
    On the Payment tab page in the Enter Vendor Credit Memo,the system doesn't display field Invoice Reference to input Invoice document number of an invoice reference exists.
    Please tell me how to configure to display field Invoice Reference
    Thank in advance
    Minh

  • Error while creating the HTTP client with destination GB_DPSRetrieve

    Hi All,
    It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
    Please find the error log below and throw some light why the HTTP adapter is getting error -
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
      <SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
      <SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
      <SAP:Service>GGMailbox</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>SAP_DEV_ERP2005</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</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>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
      <SAP:P1>GB_DPSRetrieve</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    - <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="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <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>20071121</SAP:Date>
      <SAP:Time>155130</SAP:Time>
      <SAP:Host>lbsth-tb1ci</SAP:Host>
      <SAP:SystemId>XIS</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PISUPER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <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">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>0</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>15</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
      </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="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
      <Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</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" />
      </SOAP:Body>
      </SOAP:Envelope>
    Regards,
    Kishore

    Hi,
    In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
    If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
    Also check if the Target system can be reached from the XI server to validate the configuration parameters.
    Regards,
    S.Santhosh Kumar

  • Error while creating the HTTP client with destination

    Hi ,
    I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
    Error while creating the HTTP client with destination
    The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
    We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

    Check few things..
    1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
    2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
    3) Make sure certificate is installed as expected.
    4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

  • Credit memo -- with ref to invoice

    Hello All,
    This is my scenario:
    1 Invoice with value 100.
    2 Credit memo whith value 100 with ref. to invoice.
    3 The system let me create more credit memos for the same invoice exceeding de invoice original value. (it just informes me that there are other credit memos) How can I prevent this ?
    I checked copy control and Pos./neg. quantity--i put as "+" and in Item Category TAN- Completion Rule  mark as "A".
    Regards,
    Ashu

    Hi Ashutosh singh
    Credit Memo and the invoice are different and the two r used in different scenarioes
    Credit Memo is the Billing document raised for compensating the customer and the the document is raised with reference to the the Credit Memo request
    The scenarios is that the customer places an order with the company and the company delivers the fgoods to the customer in which some of thm are dmaged and the customer then claims for the compensation , so the company asks the customer to return the goods to the company and simultaneously they will pay the compensation
    process flow is as
    Created the standard order OR
    then do the deliver LF
    then billing document F2
    and then raise the credit memo request for the goods G2
    thenBilling which is the credit memo
    G2
    This is the special process where the goods are received and the customer does not want the replacement of the dmaged goods and instead he wants the amout to be credited
    so we have to raise the credit meemo request with reference to the standard illing document and then the credit memo request and then billing document G@
    but in the standsrd invoice we havae to creatae the created the standsrd and then the delivery and then the invoice
    Invoice
    order (VA01)>Delivery(VL01N)>Change Delivery(VL02N)&PGI>INVOICE
    EX:
    Order type:OR
    credit memo:
    for the return material or discount is missing for the material,we create credit memo request.credit memo has sent to customer
    order (VA01)>CREDIT MEMO(VF01).
    NO DELIVERY PROCESS.WITH REF. to BILLING DOCUMENT,we create credit memo request.
    EX:
    Order type:G2.
    The below link will help u
    http://able.harvard.edu/ar/wi/create-credit-memo.pdf
    http://web.mit.edu/sapr3/windocs/fopcs06f.htm
    Reward if useful to u

  • Create Credit Memo with Reference to Multiple Documents

    Hi.  I have the challenge of Creating a Credit Memo via VA01 referencing Multiple Billing Documents.  Anyone know any tricks to be able to reference Multiple Billing Documents in batch? 
    Cheers,
    Jerry Tischer
    Message was edited by:
            Jerry Tischer

    Hi Kamlesh,
    I think except for the Sold-to-party (which ensures same account assignment group, ur 5th point) all other can be modified in VA01. From the Billing Date of Ref Inv it takes the "pricing date" if they are different then "invoice splitting" happens for the credit / Debit memo request. Similar thing happen in case of different "terms of payment", "Inco Term" etc.
    Thanks,
    Ashish

  • Credit note from a credit memo with reference - Pricing

    Hi Gurus,
    I have created a Credit Memo (CR) with reference to an invoice (F2). The pricing procedure in the F2 is copied to CR, following the copy control defined. (what I expected).
    However, when creating the credit note (G2), the pricing procedure selected is the one defined for credit notes, and not the one in the credit memo. (I didn't expect this).
    I have this config. in the system:
    - XD03: Cust.Pricing Proced: "1"
    - VOV8: Docum.Pricing Proced: "P"
    - OVKK: for the combination of Sales ORgDCH"P"+"1" --> pricing procedure is ZPROAC  (this is pricing procedure for G2.
    The pricing procedure in the Credit Memo (CR) is ZNETO1.
    Copy control config is the following:
    - VTFA:  G2 - CR.
    Copy requirements at header level: 001
    At item cat. (G2N): copy requirement: 002 Item/order-related; Data VBRK/VBRP: 002 Ord-rel.credit memo
    Pricing type: G
    Could you provide any comments here?
    Thanks
    Julian

    Dear Julian,
    First of all Copy control does not controls the copying of pricing procedure from one doc to another.
    Pricing procedure will be same as per your pricing procedure determination.
    It controls the copying of values for particular condition types from one doc to another.
    I have created a Credit Memo (CR) with reference to an invoice (F2). The pricing procedure in the F2 is copied to CR, following the copy control defined. (what I expected).
    In this case I think Pricing procedure defined for both doc types F2 and CR is same, thats why all the pricing is copied as it is to CR.
    if they are not same but all the condition types which are there in pricing poc. of F2 are also in pricing proc. of CR then pricing values will be copied without any change. (Still sequence of condition types in pricing proc. can make diff.)
    pricing procedure is ZPROAC (this is pricing procedure for G2.
    The pricing procedure in the Credit Memo (CR) is ZNETO1
    Since the pricing procedure is different for both doc types, There could be some condition type which are there in ZNETO1 but not in ZPROAC.
    Which ever condition types are common will be copied.
    I will suggest you to keep pricing procedure same for both the doc types CR and G2.
    Or atleast all condition types of ZNETO1 should be there in ZPROAC in appropriate sequence. (ZPROAC can have addition condition types as per your requirement.)
    Regards
    Mayank

  • Is it possible to create a Credit memo without reference doc

    Hi,
    I need to create a billing document (VF01) without passing the refernce document number. Is there any way to create this? While creating the billing document i just want to pass only items.
    Thanks In Advance,
    Regards,
    Raj

    the answer is that you can create a Credit Memo request (sales document) without a reference to a billing document. The settings for this are maintained in
    SPRO>Sales and Distribution>Sales>Sales Documents>Sales Document Header>Define Sales Document Types
    In the sales document type, the field that controls whether a reference document is necessary is in the General Control pane and is called "Reference Mandatory" - BEZOB
    If that field is blank you don't need a reference number. You can also generate the actual Credit Note (billing document) without any problems. All accounting entries are carried out as normal.
    SAP help says:
    Reference mandatory
    Indicates whether, when you create a sales document, a reference document is mandatory. If so, the indicator also specifies which type ofreference document you should use.
    Use
    When you try to create a sales document that has a mandatory reference document, the system automatically prompts you for the number of the reference document.

Maybe you are looking for