Co-payment of an Order using 2 "payers" - multiple materials

G'day
I am working on a requirement to fix and improve a co-payment process. This was not set up by me - set up simply for a implemtation last year.
I am looking at alternatives with less problems.
The scenario is that a patient orders medical goods, but only pays for part of them. A second party pays the balance.
We require 2 "Invoices".
The current solution works by having a copy of the payer partner in the order and by using a manual header condition to enter what the patient pays. This changes the net price of the order. 
A debit memo is then initiated from a user exit on order save to credit a debit memo against the second paying party (Hospital or medical insurance company).
Both "payers" then have open items on their AR accounts.
The process however falls down when not all materials in an order are avaialble on the same date and we have more than one delivery. The header condition is then split over 2 Invoices and this leads to confusion in returns and credit memo's with reference to the original order.
I just wanted to put this out there and see if anyone has any better alternate ideas.
I have looked at the SAP help for the IS-Health industry solution and initial views are that they have a "co-pay" solution but it is in FI only and not SD.
My perception thus far is to continue and fix and control the behaviour of the condition via pricing formula's, requirements and possible user exits (enhancements spots).
Wondered if anyone has any better ideas.
I am an senior SD functional but have a good understanding of abap and can cut simple code and have been developer before my SAP life many years ago so can understansd technical and fucntional solutions, custom tables etc etc
Thanks in anticipation
Derrick

Does this configuration make each GigE
capabale device send data to others at GigE speeds
(eg. MacPro to ReadyNAS, MacPro to Mac Mini,
etc)?
Yes, they are all Gigabit, but if you have multiple transfers going on at once, you are limited to the speed of the backplane of the switch.
Is
there any latency or collisions caused by this
configuration?
Prehaps a crossover cable between the switches would help. In the old days you would have had to do that, but the ports are now figuring it out on their own. It might just be more efficent go by a crossover cable (looks just like a ethernet cable but has one of the internal pairs crossed, I think- that's the idea anyway.)
Many, Many.   Mac OS X (10.4.9)   Full time tech.

Similar Messages

  • Creating a PO Using BAPI For Multiple PLants Or Multiple Line Items

    Hi All
        Can you please suggest me how to create a Purchase Order Using BAPI_PO_Create1 for Multiple Plants Or for Multiple Line items. The Requirement is like the PO is for single material for single vendor but for mulple stores i.e plants
    NOte:  Suggest me the  Creation of PO for MUltiple Line items or for multiple plants Using BAPI . Hope you people will give me the needful.
    Regards
    Shivakumar Bandari

    Hi,
    Here is the sample code to do that...
    *---> po header data
      wa_poheader-vendor    =  your vendor..
      wa_poheader-doc_type  =  Your doc type..check with Functional contact....
      wa_poheader-purch_org =  Purchasing Org..
      wa_poheader-pur_group =  Purchasing Group
    *---> po header data (change toolbar)
      wa_poheaderx-vendor    =  'X'.
      wa_poheaderx-doc_type  =  'X'.
      wa_poheaderx-purch_org =  'X'.
      wa_poheaderx-pur_group =  'X'.
    *---> poitem data
    data: item like ekpo-ebelp.
    item = '0010'.
    loop at t_parts.
      it_poitem-po_item  =  '00010'.
      IT_POITEM-PLANT    =  Plant..
      IT_POITEM-STGE_LOC =  Sloc...
    *---> poitemx (item data change toolbar)
      it_poitemx-po_item  =  '0010'.
      it_poitemx-po_itemx  =  'X'.
      IT_POITEMX-PLANT    =  'X'.
      IT_POITEMX-STGE_LOC =  'X'.
    *---> add record's to internal table
      APPEND:  it_poitem,
             it_poitemx.
    endloop.
    *call bapi_po_create1
      CLEAR v_ebeln.
      CALL FUNCTION 'BAPI_PO_CREATE1'
        EXPORTING
          poheader         = wa_poheader
          poheaderx        = wa_poheaderx
        IMPORTING
          exppurchaseorder = v_ebeln
        TABLES
          return           = it_return
          poitem           = it_poitem
          poitemx          = it_poitemx.
    *---> check the return table for error message
      READ TABLE it_return WITH KEY type = 'E'.
      IF sy-subrc NE 0.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
      endif.
    Thanks,
    Murali

  • Down Payment processing for Sales orders using Milestone Billing Plan

    Hi,
    The business scenario is as follows.
    The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
    Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
    The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
    If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
    Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
    Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
    As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
    Is this the right solution?
    Can you please give the steps in detail to implement this functionality for above scenario?
    We are using SAP 4.7 version without Project Systems.
    Thanks in advance.
    Regards,
    Ragesh

    Hi Ragesh
    Check the links where you will get the entire down-payment configuration
    [https://forums.sdn.sap.com/post!replydownpayments ]
    Regards
    Srinath

  • How to use BAPI_SALESORDER_CHANGE to change payment terms in Orders?

    Can any body give me an idea on how to use BAPI_SALESORDER_CHANGE to change payment terms in Orders?
    Regards,
    Dantham Conpolwedson

    Hi,
    try the link
    Link:[https://forums.sdn.sap.com/click.jspa?searchID=24060901&messageID=7265357]

  • TS1702 Just a few minutes ago i tried to purchase from The Simpsons tapped out game, but there were a warning that my purchese was declined and i was asked to re-filled the payment info in order to compete my purchase. I did that but that wont work

    Just a few minutes ago i tried to purchase from The Simpsons tapped out game, but there were a warning that my purchese was declined and i was asked to re-filled the payment info in order to compete my purchase. I did that but that wont work and the warning keep showing up. Whats wrong? help please.. Is there any correlation with the software update? I did check the update , there is an update for iOS 6.0.1 .

    Contact iTunes Customer Service and request assistance
    Use this Link  >  Apple  Support  iTunes Store  Contact

  • Down payment against Purchase order

    Hi SAP GURU
    i have one queries regarding down payment made against asset puchase order
    I created one asset code, create the PO with accoun assignment categories A, made a advance payment against reference to this PO no .
    when i enter the po number in purchase document field, immediatly asset number coming and showing error message
    You cannot use this transaction type to post to this asset
    Message no. AA834
    Diagnosis
    The transaction type entered belongs to transaction type group 15. According to the specifications for this transaction type group, posting with transactions types belonging to this group are only allowed in specific asset classes (for example, asset classes for assets under construction).
    The asset to which you are posting belongs to class 9000 (chart of depreciation SHV). You cannot post to this class using the transaction type you have entered.
    Procedure
    Check the asset number entered. You may want to allow posting with this transaction type group for the asset class of the asset.
    Can any body suggest what is the right way for the whole scenarion , or i am making some mistake .
    points will be awarded for useful answers
    with regards
    sai krishna

    last week i also faced this problem.
    Please refer sap note number 310368 valuated goods receipt paragraph and they have clearly mentioned about making down payments against asset purchase order without getting debited to asset account.
    You have to make F5 378 message number to be a warning message instead of error message and you have to suppress asset related settings in OB41 posting keys 29 and 39. Posting key 39 is useful when you have down payment request.
    If you have done this, then it will show only warning message during down payment that "purchase order is related to asset" and it will not be debited to asset account. Also after following the above steps, it is not necessary for you to give Acquisition: down payments G/L and Down payment clearing G/L in AO90 transaction code.

  • Advance payment against Purchase order/Work Order: F-47

    Hi SAP Gurus,
    Our Client's requirement is as follows u2013
    Advance payment against Purchase order/Work Order:
    1. Advance should be PO/WO wise & not item wise.
    2. Advance should not exceed total PO/WO value.
    3. Advance against PO should include taxes & conditions maintained in PO/WO
    When I put the purchase order number along with the item number, it is taking into account the basic price for that specific item. This amount is excluding Tax.
    Actually the advance is given against the Purchase Order. So whether it is possible to
    1. Remove the mandatory filed of  Item number against the PO?
    2. Whether the amount of the advance should be inclusive of the Tax?
    Regards,
    Amit

    Amit kulkarni,
    For this requirement you have to do validation of the amount field for advance payment againest PO.
    i thiought this is only way to get your requirement
    May be this information is useful to you
    Regards
    Surya

  • Problem while creating sales order using BAPI

    Hi all,
    i am creating a sales order from the purchase order data.
    when my client will send a PO in EDI format, my 3rd party edi tool will convert that edi formatted PO to text format. then i will upload that text formatted PO to my program then i will create a SO from those uploaded PO data using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
      but,no sales order is being created.& also i am not getting any return message.by debugging also, i am not getting the error.plz suggest where i am doing mistake.below is the coding.
    DATA:
      gfilename LIKE rlgrap-filename.
    *--Internal tables
    DATA: BEGIN OF i_item OCCURS 50.    "Create Material Document Item
            INCLUDE STRUCTURE BAPISDITM .
    DATA: END OF i_item .
    DATA: BEGIN OF i_partner OCCURS 20.  "Return parameter
            INCLUDE STRUCTURE BAPIPARNR.
    DATA: END OF i_partner.
    DATA: BEGIN OF i_schedule OCCURS 20.  "Return parameter
            INCLUDE STRUCTURE BAPISCHDL .
    DATA: END OF i_schedule.
    DATA: BEGIN OF i_cond OCCURS 20.  "Return parameter
            INCLUDE STRUCTURE BAPICOND .
    DATA: END OF i_cond.
    DATA: BEGIN OF i_part OCCURS 0,     " Internal table for split data
            part(20),
          END OF i_part.
    DATA: BEGIN OF i_return OCCURS 20.  "Return parameter
            INCLUDE STRUCTURE bapiret2.
    DATA: END OF i_return.
    *-- Work areas
    DATA: BEGIN OF wa_header .       "sales Document Header Data
            INCLUDE STRUCTURE BAPISDHD1.
    DATA: END OF wa_header .
    *DATA: BEGIN OF wa_return .       "Output Structure
           INCLUDE STRUCTURE BAPIRET2.
    *DATA: END OF wa_return .
    DATA: begin of sorder.
         INCLUDE STRUCTURE BAPIVBELN.
    DATA: end of sorder.
    data:begin of t_upload,
         ebeln(10),  "PO no(seagate)
         aedat like sy-datum , "PO date
         bsart(4) , "PO type
         vdatu like sy-datum , "requested delivery date
         kunnr(10) , "customer no-sold-to-party
        kunak like vbak-kunnr, "bill-to-party
         name1_s(20), "name1 of sold-to-party
         name2_s(15), "name2 of sold-to-party
         land1_s(3), "country
         ort01_s(10),  "city
         regio_s(3), "region(state/province)
         pstlz_s(10), "postal code
         adrnr_s(10), "address
         bstkd_e(10), "end customer purchase order
         posex(6),     "end customer PO line no(item no)
         kdmat(18),     "end customer material no(part no)
         kunag(10),     "ship-to-party
         name1_c(20),   "name1 of ship-to-party
         name2_c(15),   "name2 of ship-to-party
         land1_c(3),   "country
         ort01_c(10),    "city
         regio_c(3),   "region(state/province)
         pstlz_c(10),   "postal code
         adrnr_c(10),   "address
         posnr(6), "item no(seagate PO line no)
         pstyv(4), "item category
         matnr(18), "material no(seagate 9 digit part no)
         zmeng(13), "Target quantity in sales unit
        vrkme like vbap-vrkme, "sales unit
         meins(3), "UOM
        posnr_tot like vbap-posnr,"Total no. of line items
         werks(4), "plant
        vstel like vbap-vstel, "shipping point
         empst(10), "receiving point
         shtyp(4), "shipment type
         route(6), "route
         vsbed(2), "shipping conds
        rkfkf like vbap-rkfkf, "method of billing for co/ppc orders
         zterm(4), "terms of payment key
         inco1(3), "F.O.B inco term1
         inco2(3), "F.O.B inco term2
         end of t_upload.
    Data: wa_upload like t_upload,
           i_upload like standard table of t_upload.
    Data:v_kunnr like kna1-kunnr,
          v_posnr like vbap-posnr,
          v_matnr like vbap-matnr,
          v_zmeng like vbap-zmeng,
          v_kunag like kna1-kunnr.
    *---Constants
    CONSTANTS: c_comma TYPE c VALUE ',',   " For splitting data at commas
               c_01(2) TYPE c VALUE '01',  " For movement code in Bapi
               c_b     TYPE c VALUE 'B',   " For mvt. Indicator in Bapi
               c_creat(5) TYPE c VALUE 'CREAT', " For button text
               c_clear(5) TYPE c VALUE 'CLEAR', " For clear button
               c_mvmt(4) TYPE c VALUE 'MVMT',
               c_ok(2)   TYPE c VALUE 'OK',
               c_error(5) TYPE c VALUE 'Error'.
    *--SELECTION SCREEN DESIGN--
    SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
    PARAMETERS:     
                p_auart LIKE vbak-auart, " order type
                p_vkorg LIKE vbak-vkorg, " sales org
                p_vtweg LIKE vbak-vtweg, " dist channel
                p_spart LIKE vbak-spart, " division
                p_vkgrp LIKE vbak-vkgrp, " sales group
                p_vkbur LIKE vbak-vkbur, "sales office
                p_file(256) default 'c:/saleorder.txt'.         "File name
    SELECTION-SCREEN END OF BLOCK blk1.
    SELECTION-SCREEN PUSHBUTTON 15(10) v_create USER-COMMAND creat.
    SELECTION-SCREEN PUSHBUTTON 40(10) v_clear USER-COMMAND clear.
      INITIALIZATION -
    INITIALIZATION.
      v_create = c_creat .
      v_clear = c_clear.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    PERFORM selectfile USING p_file.
    *--AT SELECTION_SCREEN--
    AT SELECTION-SCREEN .
      IF sy-ucomm = c_clear.
        PERFORM f_clear.
    ELSE.
       IF sy-ucomm <> c_mvmt.
    **--- Validating the input data.
         PERFORM f_check_inputs.
        ELSEif sy-ucomm = c_creat.
    *--- Validating the input data.
          PERFORM f_check_inputs.
    *-- Uploading the PO data.
          PERFORM f_PO_upload.
    *---checking the PO data
         PERFORM f_check_upload_data.
    *---create sales order from PO data
        PERFORM f_Sales_order_create.
        ENDIF.
    FORM f_PO_upload.
    gfilename = p_file.
      CALL FUNCTION 'WS_UPLOAD'
           EXPORTING
                filename                = gfilename
                filetype                = 'DAT'
           TABLES
                data_tab                = i_upload
           EXCEPTIONS
                conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_type            = 4
                no_batch                = 5
                unknown_error           = 6
                invalid_table_width     = 7
                gui_refuse_filetransfer = 8
                customer_error          = 9
                OTHERS                  = 10.
      IF sy-subrc <> 0.
        MESSAGE i398(00) WITH '(WS_UPLOAD)'
        ' Errors occured with exception '
         sy-subrc.
      ENDIF.
    ENDFORM.                    " f_PO_upload
    *&      Form  selectfile
          text
         -->P_P_FILE  text
    FORM selectfile CHANGING value(filename) TYPE c.
    CALL FUNCTION 'WS_FILENAME_GET'
           EXPORTING
                def_filename     = gfilename
                def_path         = 'C:\'
                mask             = ',*.txt.'
                mode             = 'O'
                title            = 'Select File Name'
           IMPORTING
                filename         = filename
           EXCEPTIONS
                inv_winsys       = 1
                no_batch         = 2
                selection_cancel = 3
                selection_error  = 4
                OTHERS           = 5.
    ENDFORM.                    " selectfile
    FORM f_Sales_order_create.
      PERFORM f_fill_header.
      PERFORM f_fill_partner.
      PERFORM f_fill_item.
      PERFORM f_call_BAPI.
    ENDFORM.                    " f_Sales_order_create
    *&      Form  f_fill_header
          text
    -->  p1        text
    <--  p2        text
    FORM f_fill_header.
    move p_auart to wa_header-doc_type.
    move p_vkorg to wa_header-sales_org.
    move p_vtweg to wa_header-distr_chan.
    move p_spart to wa_header-division.
    move p_vkgrp to wa_header-sales_grp.
    move p_vkbur to wa_header-sales_off.
    Read table i_upload into wa_upload index 1.
    move wa_upload-ebeln to wa_header-purch_no_c.
    move wa_upload-aedat to wa_header-purch_date.
    move wa_upload-bsart to wa_header-po_method.
    move wa_upload-vdatu to wa_header-req_date_h.
    move wa_upload-bstkd_e to wa_header-purch_no_s.
    *move wa_upload-route to wa_header-route.
    move wa_upload-vsbed to wa_header-ship_cond.
    move wa_upload-empst to wa_header-rec_point.
    move wa_upload-shtyp to wa_header-ship_type.
    move wa_upload-zterm to wa_header-pmnttrms.
    move wa_upload-inco1 to wa_header-incoterms1.
    move wa_upload-inco2 to wa_header-incoterms2.
    ENDFORM.                    " f_fill_header
    *&      Form  f_fill_partner
          text
    -->  p1        text
    <--  p2        text
    FORM f_fill_partner.
    if not wa_upload-kunnr is initial.
    select single kunnr from kna1 into v_kunnr
                where kunnr = wa_upload-kunnr.
    if sy-subrc <> 0.
    Message E014 with 'customer does not exist'.
    else.
    move 'AG' to i_partner-partn_role.
    move wa_upload-kunnr to i_partner-partn_numb.
    move wa_upload-land1_s to i_partner-country.
    move wa_upload-name1_s to i_partner-name.
    move wa_upload-name2_s to i_partner-name_2.
    move wa_upload-ort01_s to i_partner-city.
    move wa_upload-regio_s to i_partner-region.
    move wa_upload-pstlz_s to i_partner-postl_code.
    move wa_upload-adrnr_s to i_partner-address.
    append i_partner.
    endif.
    endif.
    if not wa_upload-kunag is initial.
    select single kunnr from kna1 into v_kunag
                where kunnr = wa_upload-kunag.
    if sy-subrc <> 0.
    Message E015 with 'end customer does not exist'.
    else.
    move 'WE' to i_partner-partn_role.
    move wa_upload-kunag to i_partner-partn_numb.
    move wa_upload-land1_c to i_partner-country.
    move wa_upload-name1_c to i_partner-name.
    move wa_upload-name2_c to i_partner-name_2.
    move wa_upload-ort01_c to i_partner-city.
    move wa_upload-regio_c to i_partner-region.
    move wa_upload-pstlz_c to i_partner-postl_code.
    move wa_upload-adrnr_c to i_partner-address.
    append i_partner.
    endif.
    endif.
    ENDFORM.                    " f_fill_partner
    *&      Form  f_fill_item
          text
    -->  p1        text
    <--  p2        text
    FORM f_fill_item.
    loop at i_upload into wa_upload.
    if not wa_upload-matnr is initial.
    select single  maramatnr msegmenge into (v_matnr, v_zmeng) from
                       mara inner join mseg on maramatnr = msegmatnr
                       where mara~matnr = wa_upload-matnr.
    if sy-subrc <> 0.
    Message E016 with 'material no does not exist'.
    elseif v_zmeng LT wa_upload-zmeng.
    Message E017 with 'order quantity is greater than the quantity present'.
      endif.
    endif.
    move wa_upload-posnr to i_item-itm_number.
    move wa_upload-pstyv to i_item-item_categ.
    move wa_upload-matnr to i_item-material.
    move wa_upload-zmeng to i_item-target_qty.
    move wa_upload-meins to i_item-target_qu.
    move wa_upload-werks to i_item-plant.
    *move wa_upload-meins to wa_vbap-meins.
    *move wa_upload-posnr_tot to wa_vbap-posnr_tot.
    move wa_upload-posex to i_item-po_itm_no.
    move wa_upload-kdmat to i_item-cust_mat22.
    move wa_upload-inco1 to i_item-incoterms1.
    move wa_upload-inco2 to i_item-incoterms2.
    move wa_upload-zterm to i_item-pmnttrms.
    move wa_upload-empst to i_item-rec_point.
    move wa_upload-shtyp to i_item-ship_type.
    move wa_upload-route to i_item-route.
    append i_item.
    PERFORM f_fill_schedule_line.
    PERFORM f_fill_conditions.
    ENDLOOP.
    ENDFORM.                    " f_fill_item
    *&      Form  f_fill_schedule_line
          text
    -->  p1        text
    <--  p2        text
    FORM f_fill_schedule_line.
    move wa_upload-matnr to i_schedule-itm_number.
    move sy-datum to i_schedule-req_date.
    move wa_upload-zmeng to i_schedule-req_qty.
    append i_schedule.
    ENDFORM.                    " f_fill_schedule_line
    *&      Form  f_fill_conditions
          text
    -->  p1        text
    <--  p2        text
    FORM f_fill_conditions.
    move wa_upload-matnr to i_cond-itm_number.
    move sy-datum to i_cond-conpricdat.
    append i_cond.
    ENDFORM.                    " f_fill_conditions
    *&      Form  f_clear
          text
    -->  p1        text
    <--  p2        text
    FORM f_clear.
    clear:p_auart,
          p_vkorg,
          p_vtweg,
          p_spart,
          p_vkgrp,
          p_vkbur.
    ENDFORM.                    " f_clear
    *&      Form  f_call_BAPI
          text
    -->  p1        text
    <--  p2        text
    FORM f_call_BAPI.
    clear:i_item,i_partner,i_schedule.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
      SALESDOCUMENTIN               =
        ORDER_HEADER_IN               = wa_header
      ORDER_HEADER_INX              =
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
    IMPORTING
       SALESDOCUMENT                  = sorder
      TABLES
      RETURN                        =
       ORDER_ITEMS_IN                 = i_item
      ORDER_ITEMS_INX               =
        ORDER_PARTNERS                = i_partner
       ORDER_SCHEDULES_IN             = i_schedule
      ORDER_SCHEDULES_INX           =
      ORDER_CONDITIONS_IN            = i_cond.
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
    if not ( sorder-vbeln is initial ).
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    write: /'Order number:', sorder.
    else.
    loop at i_return.
    write: / i_return-id, i_return-number, i_return-message(80).
    endloop.
    *write: /'Error'.
    endif.
    *loop at i_return.
    *write: / i_return-id, i_return-number, i_return-message(80).
    *endloop.
    ENDFORM.                    " f_call_BAPI

    HI
      Pricing will be carried basing on the pricing
    procedure.
    Case1: Prices will be carried out automatically if
    necessary condition records are maintained for the
    condition type.
      For this you can go to Sales Order-> Item Conditions
    In the screen you can click on command button Analysis,
    which gives you the list of condition types associated
    to the pricing procedure. By clicking on the condition
    type you can know the action that has taken place.
    Case2: Manually forcing prices for Items.
      To do this, you have to populate ORDER_CONDITIONS_IN &
    ORDER_CONDITIONS_INX. Also note to identify the item
    numbers, you manually pass the item number for each item
    in the sales order, use the same item number for
    populating conditions.
      Parameters required:
    ORDER_CONDITIONS_IN:
      ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
    ORDER_CONDITIONS_INX:
      ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
       Hope the above info helps you. Do revert back if you
    need more info.
    Kind Regards
    Eswar

  • Changing terms of payment on an order

    Hello Everyone,
    There is a big issue at my company and I am hoping someone can help me out with this. There are occasions when a customer will come into one of our branches and place an order on their account that has the terms of payment set to cash. The order will flow through our system and not hit VKM1 for credit check. Once the customer gets the product they will say they don't have the cash and they want it to go open account terms. Our branch employee will then go into VA02 and change the terms of payment on the order after post goods issue so the order will not get credit checked in VKM1 and the amount will go open account. We will end up not getting paid for this merchandise. Is there any way to put a block on this change after post goods issue in VA02? I was told that no credit checking can be done once the order gets to that point. Please help.
    James

    Item Payment terms is not available in SAP E-Commerce without enhancements.
    Since the item update event doesn't include this field in the backend interface, the best approach is to use "Extension data" fields at item level to add this feature. The update of the backend "model" needs to be done using ABAP in the item extension BAdI. ( I am assuming crmstandard scenario).
    You can use the "same" JSP code with little modification to read the item payment terms field. The valuehelp used in the header can be used for item too. From JSP, you can add the field value to extension data of Items in the SalesDocumentParser's customer exit for item.
    This new custom field has to be read in the item BAdI and later added to the Item payment term in the backend order object (Order_maintain).
    In the response cycle in the same item BAdI, the value then has to be read from the order object (Order_read) and added to the extension data tab.

  • Update ship-to partner in sales order using BAPI_SALESORDER_CHANGE

    Dear all,
    We are trying to update the ship-to partner in a sales order using BAPI_SALESORDER_CHANGE. This is working correctly for most of our orders, so we do fill the BAPI correctly. However for some of our orders on item level a different payer is specified than on header level. However in that case the BAPI will not update the ship-to partner, but given an error message VPD 034 u2018The document must contain the same credit control areas for all payersu2019. Debugging already learned that actually the message is given not because of different credit control areas, but due to the fact that the payers and therefore the credit customers are different (although in the same credit control areas). For this reason we can not update the ship-to party of a large number of our sales orders with this BAPI. Actually we have 2 questions:
    ·         Has somebody experienced the same issue and did you manage to solve it somehow, so the BAPI could be used for this purpose of updating partner data?
    ·         Do you know other ways of updating the partners or partner address of an existing sales order in the background?
    Thanks in advance for your assistance.
    Regards,
    Satish.

    It was caused by standard SAP.

  • Pop Up of Advance Payment in Sales Order

    hi Gurus
    Actually i have a query that when i am going to create the sales order the system should pop up the dialouge box indicating the customers's advance payment
    And against that advance payment the saes order is created
    if thye sales order exceeds that advance payment
    the system should gives a pop up of indicating that amt like same in Credit control
    bcoz the customer pays in advance the money to the company for the the material which has he ordered
    so whats the setting for this
    And the Advance payment is variable means it changes daily acording to customer's order
    Suitable answers will be rewarded
    Regards
    Amol gawai
    Edited by: AMOL GAWAI on Jun 7, 2008 4:41 PM

    Dear Amol,
    I think your issue can be addressed by using Credit control area. Please do the following:
    a) Define a credit control area for the customer.
    b) Maintain credit limit as 1 Rupee T-code - FD32
    c) Whenever the customer gives you a advance payment the same shall be entered in the system thru FI route and using the while FI posting in "More Data" the relevant Credit control area should be entered.
    d) By doing the above the advance payment received from the customer shall be reflected as "Special Liability" in the Credit control area (FD33). Status Tab in FD32.
    e) Now this advance payment will act as the credit limit of the customer. So after this if the Sales order value exceeds this limit the Warning or Error message can be set.
    Hope the above works for you.
    REWARD if it helps you!!
    Regards,
    Ajinkya

  • Defaulting Payment term at Order line based on Line Bill to Customer profil

    Hi
    As per Seeded Defaulting rules payment term at Order lines is defaulting from Order Header Bill to customer profile, But as per business requirement they want payment term to default from Order line bill to customer profile
    Guess we need to build API for this and use it in OM > Setup > Rules > Defaulting we need help on how package can be setup and what parameters we can use for building this API
    Thanks
    Kamalakar.G

    Hi
    If any hints on fixing this issue do let us know this is getting urgent
    Thanks in Advance
    Kamalakar

  • Stage wise payment for Service orders

    Hi techies,
    stage wise payment for Service orders. Following items are required in SAP while creating & releasing Service Entry. Matter has detailed by following example:
    Stage wise payments for an item for eg: Rate is Rs 100 per Rmt.
    Item shall be certified as 100% and released stage wise.
    Say 60% release on deployment of machinery
    Another 20% on execution of work
    Another 10% on submission of final bill
    Balance 10% as Retention Amount.
    Please provide me the solution for release of part rate as explained above.
    Thanks in advance,
    NB

    You,can use Invoice Plan....
    In order to work with an invoicing plan according to ur requirement you mentioned, you must maintain the following settings (among others) in
    Customizing:
    Desired invoicing plan type
    Date categories
    Date descriptions
    Date proposals
    You can also specify whether the invoicing dates are to be entered/maintained manually or whether the system is to suggest them.
    You can do settings here:
    SPRO ---> MM --> Purchasing --> PO --> Invoicing plan --> see here all the settings...
    Regards,
    eswarmanu...

  • HT2534 from 2 weeks ago i cant download any application when i want to get apps ( free & not free ) itunes shows me this error : click billing info , and verify your payment information in order to make purchaeses i have already 25 $ in my account  what s

    from 2 weeks ago i cant download any application
    when i want to get apps ( free & not free ) itunes shows me this error : click billing info , and verify your payment information in order to make purchaeses
    i have already 25 $ in my account
    what should i do plz

    The terms of use of the stores state (this is from the US store, but other's will be similar) :
    The iTunes Service is available to you only in the United States, its territories, and possessions. You agree not to use or attempt to use the iTunes Service from outside these locations. Apple may use technologies to verify your compliance.

  • Incoming payments against sales order

    Hi Experts,
    Our client has a new requirement.
    They need a new program to process incoming payments against sales order.
    They need sales order included in additional selection of F-28 tcode, and clear payments against sales orders.
    Could you please guide what all changes required? I have searched on the portal but didn't find any results.
    Thanks

    Hi Juliya
    I would suggest to copy the Sales Order No in one of the reference field (Ref 1, Ref 2 or Ref3) through an exit at the time of Billing (Assumption is that one billing document will always have one sales order only). You can use the exit EXIT_SAPLV60B_008. This will be triggered when the SD Invoice is transferred to Accounting.
    Now you can use F-28 or any custom program for clearing based on these fields.
    Additionally make sure that the field you are using is not changeble after a posting has been done, You can control this through configuration. Let me know if you need any further inputs.
    Thanks & regards
    Sanil Bhandari

Maybe you are looking for

  • Close old open POs of GR and IR quantity differ.

    Hi, We are having some open POs of year 2006, 2007. These POs are not archived due to Quantity delivered differs from qty. invoiced. Now GR, IR are archived and business wants to close these POs.System is not allowing as there is difference in GR and

  • Just a happy rant

    Hi all, No question here, just a very happy rant. Last week my faithful but old ALPB finally decided to throw in the towel and call it a day after almost 7 years of service. Sad, but also a great excuse to finally upgrade. Being that I'm poor, I coul

  • Application server-file delete

    Hi All, Is there any options to delete for file in directory in Application server. If there ,please send me flow or logic.

  • Airtunes iPhone and Multiple Airport Express

    Hi, I have 2 airport express's connected to speakers....can my iPhone connect to multiple AE's with AirTunes in the iPod mode?

  • Increase CalcLockBlock setting

    I am receiving the following error message when drilling down on an ad hoc report, or generating various reports. Dynamic Calc processor cannot lock more than [50] ESM blocks during the calculation, please increase CalcLockBlock setting and then retr