Accounting Posting Problem related to Customers

We have a custom program that creates customers using function module SD_CUSTOMER_MAINTAIN_ALL. The program runs without error and returns a customer number for the new customer as expected.
When we create a contract using that customer, there is no problem. However, when we attempt to invoice the contract, accounting is not posted. We need to first open the customer using XD02 and then save the customer again -- no changes are involved -- and then we are able to invoice the contract.
I attempted to try to find out if perhaps a field were missing or not but was unable to find the difference between a customer that is created from the program and then a customer that has been re-saved. Any ideas or help would be greatly appreciated and points will be awarded.
Thanks in advance.

The problem was that in our customer creation program, we assign a default reconciliation account. Originally, the leading zeros for the account were not included. This does not result in any errors when using SD_CUSTOMER_MAINTAIN_ALL. However, by opening up and then saving the customer, the leading zeros are automatically entered.
I didn't think about this earlier but what we did was opened it and then saved it, then checked the change log to identify the problem field (Environment -> Changes).
Thanks.
Message was edited by:
        John S

Similar Messages

  • Accounts Posting Problem

    Hi SDN team
    greetings
    I have the following requirement please help me.
    the client has a salary component of Social Security Deduction. which is contributed by both Employee and Employer.
    the requirement is BOTH the entries should be passed from HR --> FI
    two wage types( deduction wage types)  for both the Employee and Employer contribution.
    when the amount is being deducted from the salary, infact the amount of ER Contribution should not be deducted from the salary, so what i have done is i have created a wage type ER contribution Payment.
    so when ever the pay roll is run it will generate 3 wage types
    1 EE contribution(deduction)
    2 ER contribution( dedution)
    3 ER contribution (Payment)
    But i dont feel this is a right practice.
    please let me know whether there is any other way to sort out this
    regards
    Prathap

    Hi Pratap,
    Pass the basis for that deduction through Infotype 14 or u can use some std /1** wage type if u think that is ok for you. write a rule to generate the deduction amount for employee and employer.
    set processing class 5 as 1 for Employee contri so it get cumulate to /550 and /700 and for employer contri set processing class 5 as 0.
    else you can pass both (Ee and Er contri amount ) through IT14 or 15 and set the processing class 5 as 1 and 0.
    but then u need to take care according to basis if deduction varied with basis.
    regards,
    Praveen
    Edited by: Praveen-Sapping in SAP World on Mar 25, 2009 9:07 PM

  • Post on account in f-58 for customers

    Hi all,
    I have simple question. when i do "post on account" in f-58 for customers,when i go back and see in fbl5n for that  customer i see that the amount is added to the open item where as when i do "post on account" for vendors the amount is deducted from the open items.
    Can any one please explain me this concept.
    Regards,
    Sneha

    Hello,
    It seems that you making the payment (return payment) to the customer on the advances that you have received from Customer. You cannot make the payment on customer invoices as these are already debit items.
    Regards,
    Ravi

  • How to solve the problem related with inputing of the text into Wordpress from Firefox 9 and 9.0.1. The problem is that after inputing the formatting gets lost. Taking in account high popularity of Wordpress I suppose the problem is quite serious.

    How to solve the problem related with inputing of the text into Wordpress from Firefox 9 and 9.0.1.
    The problem is that after inputing the formatting gets lost.
    Taking in account high popularity of Wordpress I suppose the problem is quite serious.

    Perform the suggestions mentioned in the following articles:
    * [https://support.mozilla.com/en-US/kb/Template:clearCookiesCache/ Clear Cookies & Cache]
    * [[Troubleshooting extensions and themes]]
    * Clipboard not working -> [http://kb.mozillazine.org/Clipboard_not_working]
    * Rich Text Editing -> [http://kb.mozillazine.org/Rich_text_editing]
    * Update All your Firefox Plugins -> [https://www.mozilla.org/en-US/plugincheck/]
    Check and tell if its working.
    Might not be related to your problem but some of your Plugins are out-dated
    * Update All your Firefox Plugins -> [https://www.mozilla.org/en-US/plugincheck/]
    * '''When Downloading Plugins Update setup files, Remove Checkmark from Downloading other Optional Softwares with your Plugins (e.g. Toolbars, McAfee, Google Chrome, etc.)'''

  • Joint Venture Accounting Posting Period

    What is the T-Code for opening Joint Venture Accounting Posting Period ?
    The system prompts a warning when posting an operated or non-operated cash calls
    I am new to SDN ,can anyone kindly refer to me the link where i can ask questions related to Joint Venture Accounting or Production Sharing Accounting.

    I have a problem with periods of JVA, although they are closed you can record FI documents,
    release 6.
    Best regards
    Antonella

  • FB05 posting problem using POSTING_INTERFACE_CLEARING

    Hi All,
      I have a problem posting FB05 using POSTING_INTERFACE_CLEARING.My requirement is to select open item based on document number and then create another leg for that open item using GL account,posting key and amount that matches the selected open item amount.
    I am not sure whether I am not doing the right thing because I get an error 'Difference is too large for  clearing'. If I actually go to FB05 and 'choose open item' for document number and try to hit 'Save' on the list of open items screen,I get the same error. I then  select 'Charge off difference' and it takes me to screen that is quite similar to FB01 and I enter the other leg of the entry i.e posting key,acct no,amount etc.I want to replicate the same process using funtion module.I am sending you the code,please help me.
    start-of-selection.
      i_splitinput-compcode = '0410'.
      i_splitinput-currency = 'USD'.
      i_splitinput-amount = '299'.
      i_splitinput-reference = '90286483'.
      i_splitinput-date = '20090320'.
      i_splitinput-type = 'D'.
      i_splitinput-clearingacct = '101002'.
      append i_splitinput.
      loop at i_splitinput.
        at first.
          perform posting_interface_start using 'C'.
        endat.
        at new currency.
          perform f_create_document_header using i_splitinput-compcode
                                                 i_splitinput-currency.
        endat.
        perform f_create_document_items .
        at end of currency.
          perform f_post_gl_document.
        endat.
        at last.
          perform f_posting_interface_end.
        endat.
      endloop.
    *&      Form  posting_interface_start
          text
         -->P_P_TYPE  text
    form posting_interface_start  using    p_type.
      data lv_mode type c value 'N'.
      if p_type = 'C'.
        call function 'POSTING_INTERFACE_START'
          exporting
            i_function         = 'C'
            i_mode             = lv_mode
            i_update           = 'S'
          exceptions
            client_incorrect   = 1
            function_invalid   = 2
            group_name_missing = 3
            mode_invalid       = 4
            update_invalid     = 5
            others             = 6.
        if sy-subrc <> 0.
          message 'Error initializing posting interface'(e05) type 'I'.
        endif.
      endif.
    endform.                    " posting_interface_start
    *&      Form  f_create_document_header
          text
    -->  p1        text
    <--  p2        text
    form f_create_document_header using p_compcode p_currency.
      data: l_waers type waers,
    l_postdate(10) type c,
    l_docdate(10),
    l_bktxt type bktxt,
    l_blart type blart.
    *---Convert dates to proper format MM/DD/YYYY
      write p_pstdat to l_postdate mm/dd/yyyy.
      write p_docdat to l_docdate  mm/dd/yyyy.
      i_ftpost-stype = 'K'.   "Header
      i_ftpost-count = 1.
      perform ftpost_field using: 'BKPF-BUKRS' p_compcode,  "Company Cd
                                  'BKPF-WAERS' p_currency,  "Doc Currency
                                  'BKPF-BLART' p_doctyp,  "Doc Type
                                  'BKPF-BLDAT' l_docdate,   "Doc Date
                                  'BKPF-BUDAT' l_postdate,   "Posting Dt
                                  'BKPF-BKTXT' p_doctxt,  "Header Text
                                  'BKPF-XBLNR' p_ref,     "Ref Doc
                                  'RF05A-AUGTX' 'Test'.  "Clearing item text
    *creditnote to your own
    *debit to customer but sometimes you post credit
    *payor-vendor +ve    payee-customer  -ve
      i_ftpost-count = 0.
    endform.                    " f_create_document_header
    *&      Form  ftpost_field
          text
         -->P_1045   text
         -->P_PA_BUKRS  text
    form ftpost_field using field_name type any
                            field_value type any.
      i_ftpost-fnam = field_name.
      i_ftpost-fval = field_value.
      append i_ftpost.
    endform.                    " ftpost_field
    *&      Form  f_create_document_items
          text
    -->  p1        text
    <--  p2        text
    form f_create_document_items .
    *concatenate i_splitinput
      i_ftclear-agkoa  = 'D'."D-cust, v-vend
      i_ftclear-agkon  = '1041048'."cust/ven acct
      i_ftclear-agbuk  = i_splitinput-compcode.
      i_ftclear-xnops  = 'X'.
      i_ftclear-xfifo  = space.
      i_ftclear-agums  = space.
      i_ftclear-avsid  = space.
      i_ftclear-selfd  = 'BELNR'.
      i_ftclear-selvon = i_splitinput-reference.
      i_ftclear-selbis = 'Test'.                              
      collect i_ftclear.clear i_ftclear.
    i_ftclear-selvon = '101002'.
    i_ftclear-selbis = '101002'.                           
    append i_ftclear.
      i_ftpost-stype = 'P'.  "Details
      i_ftpost-count = i_ftpost-count + 1.
      perform ftpost_field using: 'RF05A-NEWBS' '15',      "Post Key
                                  'RF05A-NEWKO' '1071990',   "GL Account
                                  'BSEG-WRBTR'  '299',     "DC Amount
                                  'BSEG-SGTXT'  'SAN'.      "Item Text
                                 'BSEG-ZUONR'  i_post-merchant_id.
    *lt_ftclear-selvon = p_doc2.
    *lt_ftclear-selbis = p_doc2.
    *APPEND lt_ftclear.
    endform.                    " f_create_document_items
    *&      Form  f_post_gl_document
          text
    -->  p1        text
    <--  p2        text
    form f_post_gl_document .
      refresh i_blntab.
      clear i_blntab.
      call function 'POSTING_INTERFACE_CLEARING'
        exporting
          i_auglv                          = 'UMBUCHNG'
          i_tcode                          = 'FB05'
        I_SGFUNCT                        = ' '
        I_NO_AUTH                        = ' '
        importing
          e_msgid                          = v_msgid
          e_msgno                          = v_msgno
          e_msgty                          = v_msgty
          e_msgv1                          = v_msgv1
          e_msgv2                          = v_msgv2
          e_msgv3                          = v_msgv3
          e_msgv4                          = v_msgv4
          e_subrc                          = g_subrc
        tables
          t_blntab                         = i_blntab
          t_ftclear                        = i_ftclear
          t_ftpost                         = i_ftpost
          t_fttax                          = i_fttax
       exceptions
         clearing_procedure_invalid       = 1
         clearing_procedure_missing       = 2
         table_t041a_empty                = 3
         transaction_code_invalid         = 4
         amount_format_error              = 5
         too_many_line_items              = 6
         company_code_invalid             = 7
         screen_not_found                 = 8
         no_authorization                 = 9
         others                           = 10
      if sy-subrc <> 0.
        v_message = 'Posting Interface Error.'.
      endif.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id        = v_msgid
            lang      = sy-langu
            no        = v_msgno
            v1        = v_msgv1
            v2        = v_msgv2
            v3        = v_msgv3
            v4        = v_msgv4
          IMPORTING
            msg       = v_message
          EXCEPTIONS
            not_found = 1
            OTHERS    = 2.
    WRITE : V_MESSAGE.
    endform.                    " f_post_gl_document
    *&      Form  f_posting_interface_end
          text
    -->  p1        text
    <--  p2        text
    form f_posting_interface_end .
      call function 'POSTING_INTERFACE_END'
        exporting
          i_bdcimmed              = ' '
        exceptions
          session_not_processable = 1
          others                  = 2.
      if sy-subrc <> 0.
      endif.
    endform.                    " f_posting_interface_end
    Thanks in advance.

    Hi Abaper,
      This is in continuation of my previous email,I am sending you my code.Please take a look and let me know your suggestions.Also can you please share with me your code if you have ever worked with FB05.
    Also I have debugged and found that at the end on program SAFM05A screen 0733 ,the code enters document number BELNR and does okcode - /11. This takes to the screen SAPDF05X  screen 3100 where it does try to save.I believe 3100 is a final screen according to the FM code but there is something I may not be passing which is not allowing it to save.
    *Session header
          perform populate_xbgr00.
          append xbgr00 to dataset.
        write p_docdat to p_docdat mm/dd/yy.
        write p_pstdat to p_pstdat mm/dd/yy.
    *Document header
              perform populate_xbbkpf using
                i_splitinput-compcode
                p_docdat
                p_pstdat
                p_doctyp
                 i_splitinput-currency
                sum_inprec_hd_tmp-xblnr
                'Test'.
              append xbbkpf to dataset.
    *bbseg bselk and bselp
            perform populate_xbbseg .
    *********forms
    form populate_xbgr00 .
      move '0' to xbgr00-stype.
      move 'zsan' to xbgr00-group.
      move sy-mandt to xbgr00-mandt.
      move sy-uname to xbgr00-usnam.
      move 'X' to xbgr00-xkeep.
    move space to xbgr00-xkeep.
      move '/' to xbgr00-nodata.
    endform.                    " populate_xbgr00
    form populate_xbbkpf  using  p1 p2 p3 p4 p5  p7.
      move '1' to xbbkpf-stype.
      move 'FB05' to xbbkpf-tcode.
      move p2 to xbbkpf-bldat.
      move p4 to xbbkpf-blart.
      move p1 to xbbkpf-bukrs.
      move p3 to xbbkpf-budat.
      move '/' to xbbkpf-monat.
      move p5 to xbbkpf-waers.
      move '/' to xbbkpf-kursf.
      move '/' to xbbkpf-belnr.
      move '/' to xbbkpf-wwert.
    move p6 to xbbkpf-xblnr.
      move '/' to xbbkpf-bvorg.
      move p7 to xbbkpf-bktxt.
      move '/' to xbbkpf-pargb.
      move 'UMBUCHNG' to xbbkpf-auglv.
    endform.
    form populate_xbbseg  .
      move '2' to xbbseg-stype.
      move 'BBSEG' to xbbseg-tbnam.
      move '15'  to xbbseg-newbs.
      move '100'  to xbbseg-wrbtr.
      move 'Assign'  to xbbseg-zuonr.
      move 'Itemtext'  to xbbseg-sgtxt.
      move I_SPLITINPUT-CLEARINGACCT to xbbseg-newko.        "G/L
      append xbbseg to dataset.
    xbselk-stype = '2'.
    xbselk-agkon = 'CUST0010'.
    xbselk-agbuk = i_splitinput-compcode.
    xbselk-agkoa = 'K'.
    xbselk-sende = '/'.
    xbselk-tbnam = 'BSELK'.
    XBSELK-XNOPS = 'X'.
    append xbselk to dataset.
    xbselp-stype = '2'.
    xbselp-feldn_1 = 'BELNR'.
    xbselp-slvon_1 = i_splitinput-reference.
    xbselp-slbis_1 = 'Test'.
    xbselp-tbnam = 'BSELP'.
    append xbselp to dataset.
    endform
    Edited by: abap78 on Mar 23, 2009 5:10 AM

  • How to clear G/L account posting made through MM documents/movements

    Hi Gurus,
    How to clear G/L account posting made through MM documents/movements.
    This is issue related to open item clearance .I want to clear all MM related postiongs happened through MM movements.( From PO,invoice etc)
    Regards,
    nitin

    Hi,
    Only GR/IR account is maintained as open item management. use t-code f.19 or f.13
    Regards,
    Sreekanth

  • Employee Vendor Account posting

    hi all.
    i have to configure the Vendor Accounts posting.
    there are few wage types, that need to be posted to employee vendors in FI.
    If the following wage types are to be posted, please explain me the following one.
    wage type : 1122 personal expenses
    wage type :1123 Business expenses
    symbolic account :1122
    symbolic account : 1123
    i have used the same for both wage types and symbolic accounts.
    employee vendor numbers : 50001, 50002, 50003, 50004.
    please let me know whether, under the node of Posting in IMG, should i take all these vendors and link the symbolic account or any other porcedure.like shown below.
    1122-50001
    1122-50002
    1122-50003
    1122-50004
    1123-50001
    1123-50002
    1123-50003
    1123-50004
    is this how i should link all the vendor to the concerned Symbolic accounts.
    please give me a solution. .
    waiting for your reply
    prathap

    hi all .
    i am really thankful to all of you.
    i have Basic, HRA, Transportation, Food allowance.
    for the month April, i have made the test data and confirmed that the G/L accounts are readily available in FI.there is no problem in posting.
    but when i tried to post the salary advance payment to vendor account, it is throwing error.
    i have configured, as follows
    created Symbolic account with the specification K
    assigned the symbolic account to the wage type
    assigned *0002 to the symbolic account.
    when i tried to post to accounts, it is throwing the error. i am sure that the error is only because of this.
    i have cross checked whether the vendor account is created in FI , which is available.
    please tell me apart from this configuration, any thing is missing.
    please help me.
    prathap

  • Dont want account posting while return

    Dear All
       I am facing one problem in one scenario.
    In return case i dont want one condition type to post. i dont want post one condition in that particular account. i am using the same pricing procedure for sales cycle and return sales. and that condition should be post in sales ( now it is posting correctly ) but i dont want want to post in when i create return billing document. can u please tell me how should i handle it in pricing procedure,i cant find anything in condition type about account posting. but i think i can handle in pricing procedure by using new requirement . and the logic should be while creating return order the value of that condition should pickup zero. am i right ? please give me ur guidance
    Thanks and Regards
    Bhushan Kolte

    Hi,
    Based on your requirement, two options are available.
    1. Write a new requirement ( transaction VOFM) and assign tit to condition type with a ABAP code if doc type is return the condition gets disqualified.
    2. Alternatively you can write new condition base value and make it to zero when dco type is return ( transaction VOFM) and assign it to the condition in pricing procedure

  • BAPI for transaction FB01 with account posting key

    Hi,
    I have to use a BAPI for registering Invoices into the FI module through the FB01 transaction.
    I am trying to use the standard BAPI: BAPI_ACC_DOCUMENT_POST
    The problem is that this BAPI does not manage the account posting key (field BSCHL).
    Could anyone provide help?
    Thank you very much in advance.

    It is happening here in the BAPI
    CALL FUNCTION 'FI_GET_POSTING_KEY'
             EXPORTING
                  i_ktosl       = gs_accit-ktosl
             IMPORTING
                  e_bschs       = ld_bschs
                  e_bschh       = ld_bschh
                  e_umskz       = ld_umskz
             EXCEPTIONS
                  error_message = 1.
    As max pointed out, it is dependent on the transaction key(KTOSL).
    Srinivas

  • Account posting keys involves for process of third party order

    hi
        pls tell me the process of third party order and whos account stock will be debited and tell me the account posting keys involves in this process and how it operates
    regards
    Ram
    Edited by: Ian Wong on Aug 13, 2008 7:06 PM

    THIRD PARTY SCENARIO
    In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. A sales order may consist partly or wholly of third-party items. Occasionally, you may need to let a vendor deliver items you would normally deliver yourself.
    Process Flow
    The processing of third-party orders is controlled via material types. Material types define whether a material is produced only internally, can be ordered only from third-party vendors, or whether both are possible. For example, a material that is defined as a trading good can only be ordered from a third-party vendor. However, if you manufacture your own finished products, you may also want, from time to time, to be able to order the same type of product from other vendors.
    Processing Third-Party Orders in Sales
    Third-party items can be created automatically by the system, depending on how your system is set. However, you can also change a standard item to a third-party item during sales processing manually.
    Automatic third-party order processing
    If a material is always delivered from one or more third-party vendors, you can specify in the material master that the material is a third-party item. During subsequent sales order processing, the system automatically determines the appropriate item category for a third-party item: TAS. To specify a material as a third-party item, enter BANS in the Item category group field in the Sales 2 screen of the material master record.
    Manual third-party order processing
    In the case of a material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing. For a material that you normally deliver yourself, you specify the item category group NORM in the material master.
    If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
    If address data for the ship-to party is changed in the sales order in third-party business transactions, the changed data will automatically be passed on to purchase requisition and also to the purchase order ,if one already exists. In the purchase order, you can display the address data for the ship-to party in the attributes for the item.
    You can only change the address data for the ship-to party in the sales order for third-party business transactions, and not in the purchase order.
    Processing Third-Party Orders in Purchasing
    When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
    Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
    All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order
    You process third-party items by creating a normal sales order. In overview for the order, you can then overwrite the default item category (TAN in the standard system) with the special item category for third-party items: TAS
    Billing Third-Party Orders
    If relevance for billing indicator for the item category has been set to B (relevant for order-related billing on the basis of the order quantity) in Customizing, the system includes the order in the billing due list immediately. If, however, the indicator has been set to F (relevant to order-related billing on the basis of the invoice quantity), the system does not include the order in the billing due list until an invoice from the vendor has been received and processed by the purchasing department. In the standard system, item category TAS (third-party order processing) has been given billing-relevance indicator F.
    In the first case, the third-party order is considered to be completely billed only when the invoiced quantity equals the order quantity of the sales order item. In the second case, each time a vendor invoice is received, a customer invoice is created for the quantity in the vendor invoice and the order is considered to be fully invoiced until the next vendor invoice is received.
    If you have activated billing-relevance indicator F for item categories in Customizing, billing can refer to the goods receipt quantity instead of the incoming invoice quantity.
    You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing in Customizing for copying control for billing at item level.
    FOR YOUR PROCESS Individual Purchase Orders WELL GIVE THE RIGHT SOLUTION
    Individual purchase orders are used when your customer orders goods from you that are not in stock and must be ordered from one or more external vendors.
    Process Flow
    During sales order entry, the system automatically creates a purchase requisition item. The purchasing department creates a purchase order based on the requisition and the vendor ships the goods directly to you (unlike third party order processing, where the vendor ships directly to your customer). You then ship the goods to your customer. While the goods are part of your inventory, you manage them as part of the sales order stock. Sales order stock consists of stock that is assigned to specific sales orders and cannot be used for other purposes.
    Goods receipt will be posted when ever the vendor ships the goods to our customer.
    We will do this transaction in SAP using MIGO.
    Invoice receipt is done when the Vendor sends us the invoice.. ( I.e Billing ).
    It can be done using MIRO.
    THe above two steps are standard and manual. There are many other ways that the actual process can happen. If the client follows EDI standards then the Goods receipt and Invoice receipt can be done through IDOCs automatically.
    Process Flow for 3rd Party Sales
    Customize the third party sales in summary:
    Prerequisites for 3rd party sales,
    Purchasing org,
    purchasing group,
    assign the Purchase org to company code
    assign Purchase org to plant,
    should not maintain the stock in material, it should be trading goods,
    1. Create Vendor XK01
    2. Create Material – Material Type as "Trading Goods". Item category group as "BANS".
    3. Assign Item Category TAS to Order type that you are going to use.
    4. A sale order is created and when saved a PR is generated at the background
    5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
    6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
    7. Goods receipt MIGO
    8. Goods issue
    9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales.
    10. Billing *--
    SD - 3rd party sales order Create Sales Order
    VA01
    Order Type
    Sales org, distr chnl, div
    Enter
    Sold to
    PO #
    Material
    Quantity
    Enter
    Save
    SD - 3rd party sales order View the PR that is created with a third party sales order
    VA01
    Order Number
    Goto Item Overview
    Item ->Schedule Item
    SD - 3rd party sales order View the PR that is created
    ME52N
    Key in the PR number
    Save
    SD - 3rd party sales order Assign the PR to the vendor and create PO
    ME57
    Key in the PR number
    Toggle the "Assigned Purchase Requisition"
    Execute
    Check the box next to the material
    Assign Automatically button
    Click on "Assignments" button
    Click on "Process assignment"
    The "Process Assignment Create PO" box , enter
    Drag the PR and drop in the shopping basket
    Save
    SD - 3rd party sales order Receive Goods
    MIGO_GR
    PO Number
    DN Number
    Batch tab , click on classification
    Serial Numbers tab
    Date of Production
    Flag Item OK
    Check, just in case
    Post
    Save
    SD - 3rd party sales order Create Invoice
    MIRO
    Invoice Date
    Look for the PO , state the vendor and the Material
    Check the box
    Click on "Copy"
    Purchase Order Number (bottom half of the screen)
    Amount
    State the baseline date
    Simulate & Post
    Invoice Number
    *Invoice blocked due to date variance
    SD - 3rd party sales order Create a delivery order
    VL01N
    In the order screen , go to the menu Sales Document , select "Deliver"
    Go to "picking" tab
    State the qty and save
    SD - 3rd party sales order Create a billing document
    VF01
    Ensure that the delivery document is correct in the
    Enter
    Go to edit -> Log
    Save
    Third party order processing is as follows:
    Assume three companies X, Y and Z
    X - The company,
    y - The customer
    Z - Vendor
    When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
    If he is procuring the goods, there are two methods that are generally followed:
    Method 1) After receiving the PO from Y, X creates a sales order against Y.
    Now at the same time he also creates a PO to a vendor Z to produce the goods
    Z produces the goods and supplies to X
    X receives the goods from Z
    Then X delivers the same goods to Y.
    After that X invoices Y and Z invoices X.
    Note : Here there is no direct/ Indirect relation between Z and Y.
    This process is known as Trading Process. and the Material here is created with Material type HAWA.
    The other method is a Third party order processing method:
    Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
    X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
    Now Z supplies the material to Y and acknowledges the same to X.
    Z will send a copy of delivery acknowledgement and invoice to X.
    After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
    The next step for X is to create an invoice and submit to Y
    Only after the invoice verification document is posted then only X can create an invoice for Y.
    This is the business flow that is followed for third party order configuration.
    There are few steps that have to be configured to enable the system to function as mentioned above.
    Step1)
    If you are always following a third party process for a material then you have to create the material using item category group BANS.
    The procurement type should be marked as External procurement (F) in MRP 2 view of the material master record.
    if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurement ( in house manufacturing and external procurement).
    Step 2)
    the item category in the order should be manually changed as TAS.
    For that you need to configure the item category determination
    Order type + item cat Group + Usage + High level = Item cat + Manual item cat
    OR + NORM + + = TAN + TAS
    OR + BANS + + = TAS
    Step 3)
    make sure that during the item category configuration for TAS you need to mark relevant for billing indicator as F
    step 4)
    The schedule line category for this type should be CS.
    make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requisition order immediately after the creation of the sales order and the PO to vendor is created against this purchase requisition.
    Award if Helpful,
    Regards
    Priyanka.P

  • Account posting partially done

    Hi Gurus,
    I have a Acc Posting Problem
    Sales order-delivery-billing done for 3Nos - value $4000, when posted to accounts acc document generated, while checking acc document in fb03 it is found that only $2000 is posted into account, what would be the cause for this.
    thanking you
    praveen

    Dear Praveen,
    Check in this way
    1.Check the what are elements(i.e price DiscountTax etc..) involved for total value $4000.
    2.Check the condition types in the pricing procedure is there Statistical check maintaining for some of the condition types.
    3.If the billing document released to the accounting it will transfer the value based on the pricing  value only which is arrived through pricing procedure.
    If there is any problem system will not release the billing to accounting fully9i.e there will not be ant partial releasing).
    I hope this will help you,
    Regards,
    Murali.

  • EDI - Outbound Accounting Posting Journals to External System

    Hi Experts,
    I have a requirement in which I have to outbound
    Accouting Journals to an external system...
    Does standard SAP support such a functionality.
    I looked at the outbound process code and was unable
    to find anything on accounting.  (which does make sense...) I also noticed that journal entry transactions such as FB01 do not have output controls like SD or MM.
    Would I not be able to utilize standard idocs in this case?

    Hi Rolmega,
    Please refer the OSS note 616804 .That is exactly matching your requirement and guide you through out the development.
    OSS note 616804.
    Create a BAPI which can be used to create cash journal documents.
    To do this, carry out the steps specified below in your system, or import the relevant Support Package.
    1. In Transaction SE37, select the menu option 'Goto' -> 'Function Groups' -> 'Create group'. Create function group SAPLFCJ_BAPI with the short text 'BAPI for FI cash journal' and save it.
    2. In Transaction SE37, create function module BAPI_CASHJOURNALDOC_CREATE in function group SAPLFCJ_BAPI in package CAJO with the short text 'Save FI cash journal documents' as a remote-enabled module.
    a) Create the following function module documentation for the function module:
                            With BAPI BAPI_CASHJOURNALDOC_CREATE, you can save a document when you execute in the FI cash journal, in the same way as when you make an entry via the Interface Transaction FBCJ.
                            If the TESTRUN field is set, the system only carries out the checks and not the actual backup process when the database is updated.
                            If you want to save a cash journal document, the program that calls the BAPI has to execute the COMMIT WORK to update the document.
                            A document can contain several split rows.
                            You can post either expenses or receipts for each document. In other words, either the ITEMS-P_PAYMENTS or the ITEMS-P_RECEIPTS field has to be filled in all line items.
                            If the document contains several line items or entries in the control table, assigned net or tax base amounts are deleted.
                            The initiator has to assign the item number (ITEMS-POSITION_NUMBER) for all line items or for none.
                            If the initiator assigns one-time data, the item numbers (CPD_ITEMS-POSITION_NUMBER) have to correspond to the respective line item (ITEMS-POSITION_NUMBER). The same item number may be used in one one-time line item only.
                            If the extended withholding tax is active in the company code used, you can create only one line item and no split document for vendors or customers that are relevant for withholding tax.
                            The vendor has to be filled for all assigned rows of the withholding tax information (table WTAX_ITEMS).
                            If withholding tax information is to be assigned, the indicator for withholding tax type (WTAX_ITEMS-WTAXTYPE) has to be filled with a value that is defined in the vendor master record. In addition, the same indicator for the withholding tax type may be assigned in one line of the ITEMS table only. The system does not take into account the external item number for withholding tax information.
                            In the TAX_ITEMS table, the same tax code may be assigned in only one line.
                            If there are entries in the TAX_ITEMS table, every tax code or jurisdiction code of this table has to be assigned in at least one line of the ITEMS table or be able to be derived from the Customizing for the business transaction.
                            If, in Customizing,  there are accounts and tax codes for interface transactions that are flagged as not ready for input, then the BAPI derives values that are transferred in the ITEMS table again and overwrites them if necessary.
                            A check recognizes that field HEADER-CHECK_NUMBER is filled when the BAPI is called.
                            You cannot use the BAPI to save a document in a cash journal if this cash journal is simultaneously blocked by another interface user or another BAPI initiator. When you execute the BAPI, the system also sets a block for other users.
                            The initiator of the BAPI can transfer additional field values via the EXTENSION_IN table and can process them further in a BADI called in the customer_function subroutine.
                            You cannot change saved documents or deposit checks.
    a) Enter the following import parameters:
    Parameter Name  Type  Associated Type  Opt  Pass Value  Short text
    HEADER          LIKE   BAPI_CJ_HEADER        X           Document header
      Long text:
    In the HEADER structure, you can assign the document header information of the cash journal document to be saved. Basically, the structure corresponds to the fields of the TCJ_DOCUMENTS table that are ready for input on the cash journal interface and which contain header information only.
    TESTRUN         LIKE  BAPI2021_HELP    X    X     Indicator for test run
                            TESTRUN                     without update
      Long text:
    If the TESTRUN field is set, the external structures transferred when the BAPI is called are assigned to the internal cash journal structures. The relevant checks are also carried out. However, no update occurs to save the document on the database.
    b) Enter the following export parameters:
    Parameter Name  Type  Associated Type  Pass Value Short text
    COMPANY_CODE    LIKE  BAPI_CJ_HEADER   X          Company code
                            -COMP_CODE
      Long text:
    The COMPANY_CODE parameter contains the company code of the saved cash journal document.
    CASH_JOURNAL_NUMBER LIKE BAPI_CJ_HEADER       Cash journal number
                              -CAJO_NUBMER
      Long text:
    The CASH_JOURNAL_NUMBER parameter contains the cash journal of the saved cash journal document.
    FISCAL_YEAR         LIKE BAPI_CJ_KEY   X     Fiscal year
                              -FISC_YEAR
      Long text:
    The FISCAL_YEAR parameter contains the fiscal year of the saved cash journal document, but it is only filled for check totals documents.
    CASH_JOURNAL_DOC_NO LIKE BAPI_CJ_KEY   X     Document number
                              -POSTING_NUMBER     cash journal document
      Long text:
    The CASH_JOURNAL_DOC_NO parameter contains the internal document number of the saved cash journal document.
    c) Enter the following table parameters:
    Parameter Name Type  Associated Type Optional Short text
    ITEMS           LIKE  BAPI_CJ_ITEMS            Cash journal documentitems
      Long text:
    In the ITEMS table, you can assign the information for the line items of the cash journal document to be saved. Basically, the spaces in the table fields correspond to the fields of the TCJ_POSITIONS table that are ready for input on the cash journal interface and which contain item information only. You can assign several line items per document, in the same way as for the split lines that can be entered via the interface transaction.
    TAX_ITMES     LIKE  BAPI_CJ_TAX_ITEMS  X      Cash journal tax items
      Long text:
    In the TAX_ITEMS table, you can assign tax information for the cash journal document to be saved. In this way, you can for example affect tax amounts derived from the system, in the same way as tax information is changed on the split window of the interface transaction.
    CPD_ITEMS     LIKE  BAPI_CJ_CPD_ITEMS  X      One-time data
      Long text:
    In the CPD_ITEMS table, you can assign information for one-time customers or vendors that are contained in line items of the ITEMS table. Basically, the table fields correspond to the fields of the TCJ_CPD table, which are ready for input on the one-time window.
    WTAX_ITEMS    LIKE  BAPI_CJ_WTAX_ITEMS X      Withholding tax in the
                                                    cash journal document
      Long text:
    In the WTAX_ITEMS table, you can assign information on the extended withholding tax for a vendor that is contained in a line item of the CJ_ITEMS table. Basically, the table fields correspond to the fields of the TCJ_WTAX_ITEMS table, which can be changed the withholding tax window.
    EXTENSION_IN  LIKE  BAPIPAREX          X   Container for
                                                 'Customer Exit'
      Long text:
    In the EXTENSION_IN parameter, you can transfer parameters that can be processed further in the BADI CJ_DOCUMENT, which the user of the BAPI BAPI_CASH_JOURNAL_CREATE has to implement.
    For example, you can assign data to the TCJ_POSITIONS table in the form of Include CI_COBL or information profitability segments or real estate.
    RETURN         LIKE  BAPIRET2               Return parameter
      Long text:
    In Table RETURN, the messages of the program are returned to the initiator of the BAPI.
    d) Save and activate the changes.
    1. Using Transaction SE11, create data type (structure) BAPI_CJ_HEADER in Package CAJO with the short description 'Cash journal document header for transfer to a BAPI'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
    b) Create the following fields:
    Field            Data element
    COMP_CODE        BUKRS
    CAJO_NUMBER      CJNR
    CURRENCY         WAERS
    CURRENCY_ISO     WAERS_ISO
    DOC_DATE         BLDAT
    PSTNG_DATE       BUDAT
    REF_DOC_NO       XBLNR1
    BP_NAME          CJBPNAME
    ALLOC_NMBR       DZUONR
    TEXT1            CJDOCTEXT100
    TEXT2            CJDOCTEXT30
    CHECK_NUMBER     SCKNR_EB
    CHECK_ISSUER     CJCHECKISSUER
    BANK_KEY         BANKK
    BANK_ACCT        BANKN
    BANK_CTRY        BANKS
    BANK_CTRY        BANKS
    BANK_CTRY_ISO    BANKS_ISO
    SCBANK_IND       LZBKZ
    SUPCOUNTRY       LANDL
    SUPCOUNTRY_ISO   LANDL_ISO
    c) Save and activate the changes.
    2. In Transaction SE11, create data type (structure) BAPI_CJ_ITEMS in Package CAJO with the short description 'Cash journal line item for transfer to a BAPI'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as enhancement category.
    b) Create the following fields:
    Field            Data element
    POSITION_NUMBER  CJBUZEI
    TRANSACT_NUMBER  CJTRANSNUMB
    P_RECEIPTS       BAPIWRBTR
    P_PAYMENTS       BAPIWRBTR
    P_NET_AMOUNT     BAPIWRBTR
    H_NET_PAYMENT_WT BAPIWRBTR
    GL_ACCOUNT       HKONT
    TAX_CODE         MWSKZ
    TAXJURCODE       TXJCD
    VENDOR_NO        LIFNR
    CUSTOMER         KUNNR
    POSITION_TEXT    CJPOSTEXT
    BUS_AREA         GSBER
    TR_PART_BA       PARGB
    TRADE_ID         RASSC
    CS_TRANS_T       RMVCT
    FUNC_AREA        FKBER
    CO_AREA          KOKRS
    COSTCENTER       KOSTL
    ACTTYPE          LSTAR
    ORDERID          AUFNR
    ORDER_ITNO       CO_POSNR
    CALC_MOTIVE      BEMOT
    COSTOBJECT       KSTRG
    CO_BUSPROC       CO_PRZNR
    PROFIT_CTR       PRCTR
    PART_PRCTR       PPRCTR
    WBS_ELEM         PS_POSID
    NETWORK          NPLNR
    ACTIVITY         VORNR
    ASSETMAINO       BF_ANLN1
    ASSETSUBNO       BF_ANLN2
    VALUEDATE        BF_BZDAT
    ASSETTRTYP       BF_ANBWA
    PLANT            WERKS_D
    VAL_TYPE         BWTAR_D
    MATERIAL         MATNR
    SALES_ORD        KDAUF
    SCHED_LINE       KDEIN
    S_ORD_ITEM       KDPOS
    FM_AREA          FIKRS
    FUNDS_CTR        FISTL
    CMMT_ITEM        FIPOS
    FUND             BP_GEBER
    FUNDS_RES        KBLNR_FI
    RES_ITEM         KBLPOS
    PERSON_NO        PERNR_D
    BUPLA            BUPLA
    SECCO            SECCO
    c) Save and activate the changes.
    3. In Transaction SE11, create the data type (structure) BAPI_CJ_TAX_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
    b) Create the following fields:
    Field            Data element
    TAX_CODE         MWSKZ
    AMT_TAX          BAPITXBTR
    AMT_BASE         BAPIFWBAS
    TAXJURCODE       TXJCD
    c) Save and activate the changes.
    4. In Transaction SE11, create the data type (structure) BAPI_CJ_CPD_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category
    b) Create the following fields:
    Field            Data element
    POSITION_NUMBER  CJBUZEI
    ANRED            ANRED
    NAME             NAME1_GP
    NAME_2           NAME2_GP
    NAME_3           NAME3_GP
    NAME_4           NAME4_GP
    SOLE_PROP        STKZN
    REP_NAME         REPRES
    STREET           STRAS_GP
    POSTL_CODE       PSTLZ
    CITY             ORT01_GP
    COUNTRY          LAND1_GP
    COUNTRY_ISO      LAND1_ISO
    PO_BOX           PFACH
    POBX_PCD         PSTL2
    REGION           REGIO
    POBK_CURAC       PSKTO
    BANK_ACCT        BANKN
    BANK_NO          BANKL
    BANK_CTRY        BANKS
    BANK_CTRY_ISO    BANKS_ISO
    CTRL_KEY         BKONT
    BANK_REF         BKREF
    INSTR_KEY        DTAWS
    DME_IND          DTAMS
    TAX_NO_1         STCD1
    TAX_NO_2         STCD2
    TAX_NO_3         STCD3
    TAX_NO_4         STCD4
    SLS_PUR_TX       STKZU
    FITYP            J_1AFITP_D
    TAX_NO_TY        J_1ATOID
    EQUAL_TAX        STKZA
    SPRAS            CHAR_LG_01
    LANGU_ISO        LAISO
    BUS_TYPE         GESTYP
    IND_TYPE         INDTYP
    c) Save and activate your changes.
    5. In Transaction SE11, create the data type (structure) BAPI_CJ_WTAX_ITEMS in Package CAJO with the short description 'Withholding tax in cash journal document for transfer to a BAPI'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
    b) Create the following fields:
    Field            Data element
    POSITION_NUMBER  CJBUZEI
    VENDOR_NO        LIFNR
    WTAXTYPE         WITHT
    WT_WITHCD        WT_WITHCD
    W_TAX_BASE       BAPIQSSHB
    WI_TAX_AMT       BAPIQBSHB
    c) Save and activate the changes.
    6. In Transaction SE11, create the data type (structure) BAPI_CJ_KEY in Package CAJO with the short description 'Key fields for cash journal documents'.
    a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
    b) Create the following fields:
    Field            Data element
    FISC_YEAR        GJAHR
    POSTING_NUMBER   CJBELNR
    c) Save and activate the changes.
    7. Using Transaction SE91, create the following messages for message class FCJ and select the 'Self-explanatory' field for each one:
    a) 011: 'Document & & & was saved successfully.'
    b) 012: 'Enter a gross amount.'
    c) 013: 'Enter only the disbursement or incoming payment amount for each document.
    d) 014: 'Enter the item numbers for all items or for none of them.'
    e) 015: 'The number of tax items may not be larger than the number of items.'
    f) 016: 'Only one tax item allowed per tax code/jurisdiction code.'
    g) 017: 'Enter the item number for one-time items.'
    h) 018: 'With several line items (split), do not enter any withholding tax items.'
    i) 019: 'Business transaction without G/L account or tax code.'
    j) 020: 'No line item with tax code/jurisdiction code of the tax item.'
    k) 021: 'In company code & taxes without jurisdiction code.'
    l) 022: 'Do not enter any tax item for posting indicator '3' (T007B-STBKZ)'
    m) 023: 'Document could not be saved. Correct the errors listed'
    n) 024: 'Business place + section code only with extended withholding tax.
    o) 025: 'Net/tax base is deleted for several items or tax items'
    p) 026: 'No line item corresponds to one-time item &.'
    q) 027: 'Do not enter any withholding tax info if customer not w.tax-relevant'
    r) 028: 'Do not enter any withholding tax info if vendor not w.tax-relevant'
    s) 029: 'Do not enter any withholding tax info for G/L account posting.'
    t) 030: 'Vendor in withholding tax information is not in line item.'
    u) 031: 'Only one one-time item is allowed per item number.'
    v) 032: 'Only one withholding tax item is allowed per withholding tax type.'
    w) 033: 'Number of assigned withholding tax items deviates from master data.'
    x) 034: 'No vendor required for business transaction.
    y) 035: 'No customer required for business transaction.'
    z) 036: 'Enter only receipts for checks.'
    8. In Transaction SE37, call the FCJ_SAVE and FCJ_SAVE_DOCUMENT function modules in change mode.
    a) Add import parameter I_XBAPI of TYPE BOOLEAN to these function modules. Select the Optional and Pass Value fields and enter the short text 'Indicator whether the call occurs from a BAPI'.
    b) Also add the import parameters I_POSTING_NUMBER, LIKE, ISCJ_POSTINGS-POSTING_NUMBER for the function module FCJ_SAVE_DOCUMENT. Select the Optional and Pass Value fields.
    c) Save and activate the changes.
    9. In Transaction SE37, create the function module FCJ_SAVE_DOCUMENT_BALANCE_BAPI in the function group SAPLFCJ_PROCESS_MANAGER in Package CAJO with the short text 'Save cash journal document and balances for BAPI' as an update module with  'Start immed'.
    a) Enter the following import parameters:
    Parameter Name      Type  Associated Type           Opt Pass Value
    I_COMP_CODE         LIKE  TCJ_C_JOURNALS-COMP_CODE       X
    I_CAJO_NUMBER       LIKE  TCJ_C_JOURNALS-CAJO_NUMBER     X
    I_CURRENCY           LIKE  TCJ_DOCUMENTS-CURRENCY         X
    I_TYP               TYPE   CJTRANSTYP                     X
    I_DISPLAY_PERIOD_LO LIKE  SY-DATUM                        X
    I_DISPLAY_PERIOD_HI LIKE  SY-DATUM                        X
    I_POSTING           LIKE    ISCJ_POSTINGS                  X
    I_POSTING_NUMBER    LIKE  ISCJ_POSTINGS-POSTING_NUMBER   X
    b) Enter the following tables:
    Parameter Name      Type  Associated Type
    ITCJ_POSTINGS       LIKE  ISCJ_POSTINGS
    ITCJ_WTAX_ITEMS     LIKE  TCJ_WTAX_ITEMS
    ITCJ_SPLIT_POSTINGS LIKE  ISCJ_POSTINGS
    ITCJ_CPD            LIKE  TCJ_CPD
    10. In Transaction SE18, define the BADI CJ_DOCUMENT. The corresponding interface is IF_EX_CJ_DOCUMENT.
                   The method has the following 'Changing' parameter: Parameter             Type        Associated Type
    C_ITCJ_SPLIT_POSTINGS Type        ISCJ_POSTINGS
    C_ITCJ_SPLIT_TAXES    Type        ISCJ_POSTINGS
    C_ITCJ_CPD              Type        TCJ_CPD
    C_ITCJ_WTAX_ITEMS     Type        TCJ_WTAX_ITEMS
    C_EXTENSION2           Type        BAPIPAREX
    C_RETURN                Type        BAPIRET2
                  You can use an implementation of this BADI to change the cash journal structures before the data check is processed.
    1. Implement the attached corrections in your system.
    2. In Transaction SE37, release the function module BAPI_CASHJORUNAL_DOC_CREATE via the menu path 'Function module' -> 'Release' -> 'Release'.
    3. In Transaction SWO1, create the object type BUS2023.
    a) Create the following key fields for the object type:
    Key field           Name               Data type reference
    CompanyCode       Company Code        TCJ_DOCUMENTS
                                            -COMP_CODE
    CashJournalNumber Cash Journal Number TCJ_DOCUMENTS
                                            -CAJO_NUMBER
    FiscalYear        Fiscal Year         TCJ_DOCUMENTS
                                            -FISC_YEAR
    CashJournalDocNo  Cash Journal        TCJ_DOCUMENTS
                      Document Number     -POSTING_NUMBER
    b) Create the 'Create' method synchronously and instance-independent as an 'API function' with the name BAPI_CASHJOURNALDOC_CREATE.
                            Create the following parameters for the method: Parameter          Obj Type  Imp.  Man.  Exp.
    Header             BUS2023    X     X
    Testrun            BUS2023    X
    CompanyCode          BUS2023                X
    CashJournalNumber   BUS2023                X
    FiscalYear         BUS2023                X
    CashJournalDocNo   BUS2023                X
    Items               BUS2023    X     X
    TaxItems           BUS2023    X
    CPDItems           BUS2023    X
    WTaxItems          BUS2023    X
    ExtensionIn        BUS2023    X
    Return             BUS2023                X
    a) Create the 'ExistenceCheck' method synchronously and define the following source code:
                            begin_method existencecheck changing container.
                            DATA: l_mandt TYPE sy-mandt.
                            SELECT SINGLE mandt INTO l_mandt
                            FROM tcj_documents
                             WHERE comp_code = object-key-companycode
                               AND cajo_number = object-key-cashjournalnumber
                               AND fisc_year = space
                               AND posting_number = object-key-cashjournaldocno.
                            check sy-subrc <> 0.
                            exit_object_not_found.
                            end_method.
    a) Under the menu option 'Goto' -> 'Documentation', define the following text for object type BUS2023:
                            A cash journal document is assigned to a cash journal and a company code.
                            It contains a unique document number from a company code-dependent number range interval that is independent of the number range interval of the G/L document. Cash journal documents are also numbered sequentially per company code and cash journal.
                            A cash journal document contains the offsetting entries for the G/L account of the cash journal in which G/L or person accounts are posted to for the business transaction.
                            You can save, delete, post or reverse a cash journal document. In the two last cases, there is a corresponding G/L document. This can be a receipt, a disbursement of cash, or the receipt of checks.
    1. In Transaction BDBG, set up the IDOC processing for the object type BUS2023 and the method CREATE.
                   The function module for ALE outbound processing with data refining is ALE_CASHJOURNALDOC_CREATE.
                   The function module for ALE inbound processing is called IDOC_INPUT_CAJODOC_CREATE.
    1. In Transaction 'SALE', maintain the ALE distribution. Here, maintain the steps generally required for a distribution process. Take into account the existing documentation of the operation. Execute the following steps for the BAPI used to save cash journal documents.
    a) Maintain the distribution model under the path 'Model and Implement Business Processes' -> 'Maintain Distribution Model and Distribute Views'. The object name is 'CashJournalDoc' and the method name is 'Create'.
    b) Execute the menu option 'Edit' -> 'Model view' -> 'Distribute' for the selected model view.
    c) Select the path 'Model and Implement Business Processes' -> 'Partner Profiles and Time of Processing' -> 'Generate Partner Profiles'. (See corresponding documentation in document OALE_AUTOPARTN_BD82.) Enter the selected model view in the distribution model and the selected target system as the partner system.
    2. To monitor the distribution of the IDOCs, use Transaction BD87 in both the sender system and the receiver system, and you can reach it via the path 'Tools' -> 'ALE' -> 'ALE Administration' -> 'Monitor' -> 'Status Monitor'.  The relevant message type is CASHJOURNALDOC_CREATE.

  • Account Contact problems in R17

    There is a bug in R17 where you can have an Account with Contacts in the related list, but none are the Primary Contact. Additionally, you have a Contact with Accounts in the related list, but none are the Primary Account. I've even found sitations where there IS a Primary Contact for the Account, but the person listed is NOT in the related list of Contacts. They actually are linked to yet another Account. I've not had this happen via the UI. It happens sporadically via web services.
    The CR number is 12-1YOKUCP.
    Has anybody found a reasonable work around to this problem? I'm hoping for something with defaults or workflow. I've found if you give one of the Account Contacts a Role, they become the Account's Primary Contact and their Contact record is correct.
    Regards,
    Jeff

    hi,
    you can define it in customizing which partner role consider while creating BP.
    SPRO> Cross-application Component>  SAP Business Partner --> Basic Setting .-> Business Partner Roles --> Define Application Transactions
    Select BUP1-Creat Business Partner  and click details
    Here you can specify which role u want to have while creating BP.
    Please let me know if helpful..!!!
    Regards,

  • What are the problems related when if i bought the iphone 4s or 5 unactivated ????

    what are the problems related when if i bought the iphone 4s or 5 unactivated ????

    Please restate your question with more detail. As posted, there is insufficient
    information for a response. What exactly is your technical question?

Maybe you are looking for