Due  date  calculation  in the  credit  memo

Hello,
I  need  to  have  the  same  due  date  in  the  credit  memo  as  in  original  invoice...
Is  there  any  setting  for  this?
Thanks and  best  regards
L

I doubt there is such option. From the past projects I do remember that we made a change in the form to print the document date as 'Due Date' for credit memos. Credit memos were paid at once when they were processed and I think that payment term was copied from the original invoice, which made their due date far in future.

Similar Messages

  • Due date calculation for the credit memo with invoice reference.

    Hi,
    When we create the credit memo with reference to invoice, the due date for the credit memo is getting copied from Invoice. In this case if the invoice is due on 31.12.2008 and the credit memo is created on 10.09.2009, then the credit memo due date is appearing as 31.12.2008. It should be 10.09.2009 as per the setting in VOFA billing type customisation in "Credit Memo w/vldt".
    I would like to know how to customise the below requirement.
    If the reference invoice is due after the credit memo creation, the the credit memo should due as per the invoice date.
    If the invoice due is past & then the credit memo due date should be Immediate i.e. Due Immediately.
    Thanks in advance for help.
    Regards,
    Nithin

    I doubt there is such option. From the past projects I do remember that we made a change in the form to print the document date as 'Due Date' for credit memos. Credit memos were paid at once when they were processed and I think that payment term was copied from the original invoice, which made their due date far in future.

  • Due date in A/R Credit Memo

    hi,
    do you know if there is a way to update the Due Date in A/R Credit Memo
    according to the customer's Payment Terms
    (right now Due Date = Posting Date)
    thank you,
    Rinat

    Hello Friend,
    Use Date function for installed SQL and  made FMS
    http://www.w3schools.com/sql/func_date_add.asp
    Thanks
    Manvendra Singh NIranjan
    Edited by: Manvendra Singh Niranjan on Feb 16, 2012 3:41 PM

  • How to change Net Due Date in case of Credit Memo..

    Hi Experts,
    In our system currently when we create credit memo using tcode FB75 system makes the invoive due immediately.
    We wanted to make this net due date dependent on payment terms given by us. Please let me know how can I achieve this..
    Please let me know if there is any user exit there or the configration path to achieve this...
    Regards,
    Vidya

    This is a standard SAP functionality. Usually a credit memo is referenced to an invoice and if you don't have a reference to an invoice SAP would consider that credit memo as due immediatly.
    If you have an invoice to be referenced to this credit memo enter the invoice number in the invoice reference field in FB75 > payment tab and then enter the payment term. If you don't have an invoice reference enter V  in the invoice reference field and then the payment term, system will calculate net due date based on payment term.

  • Value date in the credit memo.

    Please explain the Use of the Value Date determination of the credit memo and How Does it help in payment Reconcillation
    Also There is a Indicator in the RV document type: Credit Memo W/Value Date
    What is the consequence of flagging the same.
    Edited by: SAP Consultant on Dec 10, 2008 12:47 PM

    thanks

  • Sales Report Generation less the Credit memo

    Anybody can help me regarding Query for Sales Report. Im trying to create a sales report per Per Product and Customer with corresponding Quantity and Amount, I have already get the query the problem is I cant get the Credit Memo deduct from its A./P Invoice so that deduct the quantity and price. With this i can get the exact sales!
    Anybody have an idea? Im having headache already for a week now trying to solve this problem, Thank you very much.
    Clint

    Hi Jeyakanthan,
    Im not referring to Sales Analysis Report. All i want is to get all the sales and Less the the corresponding Credit Memo. Im trying to create a query that will show the sales, Ex.. row
    From A/R invoice Table
    DocNo CardCode   Qty   Price  DocTotal  
    0111     CA-001     10     25      250
    less from A/R Credit Memo
    DocNo CarCode    Qty   Price  DocTotal  
    0111     CA-001     5      25      125
    I want the result to deduct the row Invoice from CM.
    If the corrsponding Invoice doesnt find a CM record then the result will be 0. Ex from above data Invoice less the Credit Memo.
    if the Invoice found a Credit Memo,
    Qty1       Qty2    Qty3, DocTotal1 DocTotal2 = Result
    10   less  5      =  5 ;    250   less 125         =   125
    if the Invoice doesnt have Credit Memo,
    Qty1       Qty2    Qty3, DocTotal1 DocTotal2 = Result
    10   less  0      =  10 ;    250   less 0            =   250
    hope the will clarify everything, thank yuo very much in advance.
    Regards,
    Clint

  • The Credit Memo & Original Invoice do not have the same net due date.

    The issue is that for returns of goods from the customer, the credit memo that gets created does not have the same net due date as the original invoice.  To accomplish this, in the credit memo, the indicator "V" must be entered in the credit memo field BSEG-REBZG "Invoice Ref".  This will make the credit memo due based on the payment terms. In the OSS message 50388, SAP identifies a user exit in SDVFX008 which will fill field BSEG-REBZG with the value "V".  Doing this should automatically make the credit memo for returns due the same date as the original invoice.SAP says to do the following:
    The function module called by SDVFX008 is EXIT_SAPLV60B_008
    Make the ABAP coding in include program ZXVVFU08.
    Populate field ACCIT-REBZG with "V"
    Despite doing this , we couldnt get the same net due date as the credit memo & Original invoice.
    Can anyone help? POINTS WILL BE GIVEN.
    Thanks
    Anita

    Hi Anitha,
    Does the value 'V' gets paopulated?.
    I mean to ask whether the program goes into the user exit logic?.
    Please let me know.
    Thank you.
    Regards,
    Karun M

  • How to change the Quantity in the Credit Memo using BAPI

    Hi All,
    I have a requirement in which i need to change the Quantity Value field available in the Credit Memo using BAPI.
    Can anyone help me out to get any available BAPI to perform this action or any Solution to change the Quantity in the Credit Memo ?.
    Regards,
    Muruganand.K

    Hi,
    Try using BAPI_SALESORDER_CHANGE.
    DATA: s_order_header_in LIKE bapisdh1.
    DATA: s_order_header_inx LIKE bapisdh1x.
    DATA: BEGIN OF i_order_item_in OCCURS 0.
    INCLUDE STRUCTURE bapisditm.
    DATA: END OF i_order_item_in.
    DATA: BEGIN OF i_order_item_inx OCCURS 0.
    INCLUDE STRUCTURE bapisditmx.
    DATA: END OF i_order_item_inx.
    DATA: BEGIN OF it_return OCCURS 0.
    INCLUDE STRUCTURE bapiret2.
    DATA: END OF it_return.
    DATA: BEGIN OF i_sched OCCURS 10.
    INCLUDE STRUCTURE bapischdl.
    DATA: END OF i_sched.
    DATA: BEGIN OF i_schedx OCCURS 10.
    INCLUDE STRUCTURE bapischdlx.
    DATA: END OF i_schedx.
    s_order_header_inx-updateflag = 'U'.
    i_order_item_in-itm_number = vbap-posnr.
    i_order_item_in-TARGET_QTY = rv45a-zzqty.
    i_order_item_inx-updateflag = 'U'.
    i_order_item_inx-itm_number = vbap-posnr.
    i_order_item_inx-TARGET_QTY = 'X'.
    APPEND: i_order_item_in, i_order_item_inx.
    i_sched-itm_number = vbap-posnr.
    i_sched-sched_line = '0002'.
    i_sched-req_qty = rv45a-zzqty.
    APPEND i_sched.
    i_schedx-itm_number = vbap-posnr.
    i_schedx-sched_line = '0002'.
    i_schedx-updateflag = 'U'.
    i_schedx-req_qty = 'X'.
    APPEND i_schedx.
    IF sy-subrc = 0.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    salesdocument = xvbap-vbeln
    order_header_in = s_order_header_in
    order_header_inx = s_order_header_inx
    behave_when_error = 'P'
    TABLES
    return = it_return
    order_item_in = i_order_item_in
    order_item_inx = i_order_item_inx
    schedule_lines = i_sched
    schedule_linesx = i_schedx.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ENDIF.
    Change the fields as per your logic before populating orders item and schedule line data.
    You have to pass the quantity in schedule line items as well in case you want to change quanity in order.
    KR Jaideep,
    Edited by: Jaideep Sharma on Jun 22, 2009 7:35 PM

  • Due Date Calculation on A/R Invoice

    The Due date calculation on an Invoice for a customer with a payment condition of 30 days is wrong on  the system:
    Invoice DocDate: 11.05.17
    Invoice DueDate:  11.07.01
    On the BP Master Data is set a payment condition of 30 days. So it should be a due date of June, not July. This is a invoice that comes from a Sales Order with Approval Procedure.
    Our version is 2007 A SP:00 PL:49.
    Thanks in Advance...

    Hello,
    Perfect Notification
    For Payment Terms for Business Partner----
    IF (@transaction_type = 'A' Or @transaction_type = 'U')  AND @object_type = '17'
    BEGIN
    Declare @GroupNum as Nvarchar(20)
    Declare @OCRDGroupNum as Nvarchar(20)
    Declare @PaymentTermCode as Nvarchar(20)
    Declare @PaymentTermName as Nvarchar(20)
    Set @PaymentTermCode = (Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
    Set @PaymentTermName = (Select PymntGroup from OCTG where GroupNum = @PaymentTermCode )
    Set @GroupNum = (select GroupNum from ORDR where DocEntry =@list_of_cols_val_tab_del)
    Set @OCRDGroupNum =(Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
    If @GroupNum != @OCRDGroupNum
         begin
              SET @error = 10
              SET @error_message = N'Payment Terms Should be  ' + '   ' + @PaymentTermName + ' ' +' For this Business Partner'
         end
    END
    End----
    It will Definatillly Help You.
    Thanks
    Manvendra Singh Niranjan

  • Baseline Date for Due Date Calculation required for S/L indicators

    Hello,
    Iu2019m facing the following problem
    Iu2019m trying to insert an invoice (using a customer master record) but the system blocks me because the field ZFBDT (Baseline Date for Due Date Calculation) is a Required entry.
    The strange thing is  that if I use a S/L indicators the field is mandatory, if not the date may be defaulted.
    I checked in OB41 but there are non differences between Special PK and normal PK.
    Any ideas?
    Thanks in advance
    Alberto

    Dear Alberto,
    the field "Due On (BSEG-ZFBDT)" cannot be controlled with field status.
    It is controlled by field attribute of screen painter (Tcd: SE51).  If
    you look at element attribute for "Due On" field, a flag for required
    entry is activated.  In this case, field status has no control over
    the field.
    As of release 3.1G, field BSEG-ZFBDT is hardcoded in most FI screens
    to be mandatory and cannot be influenced by any field status
    changes. This situation is only valid when posting with special G/L
    indicator (ie PK 29/39).
    SAP development team has determined that this is a critical field.  The
    reason behind this is that this special GL screen and the data entered
    here are very important to many other programs. This data affects
    liabilities and receivables where due date is necessary almost
    everytime. Thus, we changed this field in this screen in order to
    prevent problems in many other areas. The reason is explained further
    in note 95079.
    I hope this helps You.
    mauri

  • Wrong GL Dates for Distributions for Credit Memo with Rules

    Hi all
    Using Autoinvoice, Ive created Invoice with Invoice date 17-APR-08 and 12 month payment term. Invoice line has amount of $460 and deferred accounting rule of type "Accounting, Fixed Duration". Rule start date is 17-APR-08 and duration is 1.
    I run the Revenue Recognition and then Revenue Adjustment API "ar_revenueadjust_pub.earn_revenue" to create revenue account schedule for 12 month period based on business rules. Now I issue credit memo of $60 on 18-JUN-08 with LIFO rule method and LIFO split term method, against the above invoice line.
    I run revenue recognition, go to the credit memo distributions. All the distributions show GL Date as 17-APR-08 with correct percentages and amount as in the original invoice line.
    Can anyone help me understand why all distributions of credit memo have same gl date?

    Hi Nagamohan,
    Credit Memo is applied to invoice line with deferred rule.
    If I issue credit memo on 18-JUN-08 with LIFO against a Invoice line which uses "Daily Revenue - All Periods" rule, the distributions show
    GL Date - Dr - Cr - Amount
    17-FEB-09 REV UNEARN 0.77
    17-MAR-09 REV UNEARN 39.07
    16-MAR-09 REV UNEARN 20.16
    The above amounts are exactly the reverse distributions as in Original Invoice line.
    I was expecting the same thing to happen in Deferred Fixed rule, but the only difference is for Fixed rule I cannot populate Rule_End_Date through Autoinvoice or manually.
    Kishore.
    Message was edited by:
    chakoo

  • Create IDOC when the credit memo is generated

    I want to create an IDOC.
    The IDOC will be created when the credit memo is generated.
    Please help me to create the segments.
    Title was edited by:
            Alvaro Tejada Galindo

    Hi
    First you find the relative Idoc Type and Message type for that credit memo in the tables EDBAS and EDMSG
    Then go to WE31 and create the additional segments as per your requirements apart from doing lot of other related settings
    see the doc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Regards
    Anji

  • Return to Vendor with Shipping - Help with the credit memo

    Hey guys,
    I've configured return deliveries to vendors, using a return PO with shipping, then creating an RL delivery type > transfer order> post goods issue.
    All that works fine. My trouble is trying to set up the credit memo. I'm not an SD consultant so I don't know too much about billing.
    I go to VF01 to create the billing document, however I receive an error that the delivery type (RL) is not allowed for billing type F2. I know where the config is to set up this relationship (SD>Billing>Maintain Copying Control for Billing Documents), but I would have thought a different billing type (something for credit memos) would be used instead of F2.
    In standard sales, the billing type is determined from the sales order type. As there is no sales order in this instance, where is the billing type being determined? Why is SAP trying to create my billing document with and F2 billing type.
    Thanks for you help/info,
    Mark.

    Sorry, this is not clear to me.
    If you send back goods to your vendor - generally - you send back the goods because those goods are damged. In this case it is your vendor who issues credit memo and not you to your vendor.
    MM credit memo (that is issued by your vendor) can be posted in MIRO. If your vendor issues debit memo it can be posted in MIRO too.
    Please check retrun delivery with mvt 122:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/a5/63351643a211d189410000e829fbbd/frameset.htm
    Return delivery with mvt 161:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/a5/63341243a211d189410000e829fbbd/frameset.htm
    So, I don't think you can do anything with your return delivery in VF01.
    Regards,
    Csaba

  • How to Re-execute the Credit Memo Workflow?

    Hi! Folks,
    This is a problem which I am facing @ the client site....
    Actually, I am assigned with a Credit Memo Workflow.
    Here, if the Credit Memo is created i.e. if CREATED (BO BUS2094) Event is triggered the workflow is working fine.
    But as per the requirement if they want to change the Credit Memo using VA02 tcode and if the Net Value is changed I mean if it is greater than some specific value i need to re-execute the workflow (approval process)
    As for your information, I have copied the Standard Workflow Template 20000009 & 20000019 also I have checked with Event Linkage and other workflow stuffs.
    But my main query here is that while the Credit Memo is changed, CHANGED (BO BUS2094) Event gets triggered but with Receiver Type SUBSCRIBE along with error 'CHECK FM with Exception' with Message 'No Configuration for Workflow WS90400201 version 003'
    (Here WS90400201 with version 003 is my custom workflow template (copy of WS20000019))
    Also, I want to know is there any Functional Configuration missing out because I have referred help documentation and found that this re-execution of workflow (WS20000019) is automatic.
    Just kindly let me know if any part is missed out in configuration
    Please, guys revert to the earliest.
    Regards,
    Mistry Wasim

    Hi! guys,
    Please reply with your valuable guidelines to this problem.
    Regards,
    Mistry Wasim

  • Issue related to the Credit memo and S.O.

    Hi,
    I have one issue related to the Credit memo and S.O.
    We have a network of Dealers and Dealer inventory is linked with our system. When user creates S.O for Dealer1.If the item is not avail in our inventory and it is avail in any other Dealer inventory (Dealer2), then the system creates S.O wrt the Dealer2.
    In this case as the material is directly delivered from Dealer1 to Dealer2, there is no any GI in our system.
    So, the transaction with Dealer1 will be the normal as usual. But, we have to return the goods amount to the Dealer2 with any suitable way. We are considering it as a Credit memo.
    My question is, as we have created S.O wrt the partner function- Dealer1 and we are creating CR memo for Delaer2, is there any way through which we can link the se two transactions with customizing so that we need not to make any ABAP programming.
    I mean can we create Cr memo wrt S.O when the partner functions are different?
    Pl. guide me.
    Thanks,
    Roopan.

    You have an interesting Scenario.
    You can handle this scenario in multiple ways
    1. Third party Scenario (Here Dealer 1 becomes Vendor &Dealer 2 remains Customer)
    2. Order related sales & credit memo.
    3. Intercompany sales, where you represent dealers place as a plant in your system. (Not an ideal way to handle the scenario, but possible option)
    Regards,
    Rajesh Banka
    Reward points if helpful.

Maybe you are looking for