Accounting doc standard ALE distribution

Hi all,
I need some help on a solution to set up for FI doc ALe ditstribution using standard tools.
The goal os is to send Acc doc from an R/3 to antoher R/3 system via trfc idoc, using standard messages, functions, ...
The acc docs should be sent 1/dya to the receiver system.
- If I activate standar FIDCC2 message , setting up ALE for sender & receiver, trfc ports, partner prof, ...
  in mode immediate, .. The acc docs created in sender system will be created automatcially on receiving system ?
  Is it enough or should I use an exit, BTE, .. to create the idocs ??
  My doubt is here, should I add specific code to trigger the idoc creation, or it is done automatically in this case ?
Thanks for your help,
A.F

Anyone whi can help me ?...
thanks
A.F

Similar Messages

  • Cancel billing doc with Accounting doc clearing

    Dear gurus ,
    the scenario is that  we have a billing doc with wrong pricing and the relative accounting doc has cleared status,then we use VF11 to cancel the billing doc , the system give the information  "Document #### saved (no automatic clearing)" .Message no VF216 .
    My question is,  based on the new cancellation function module AC_DOCUMENT_REVERSE, as note 1259505 description (The most evident effect of the new cancellation procedure is the automatic clearing of the accounting documents.), is that legal or illegal ,the system cancel the billing doc without checking the status of the related accounting doc ?
    IF that is the standard reaction ,how can I make some change or config to make sure that ,the billing doc with cleared  accounting doc can't not be cancelled without reseting the status of accounting doc to "not cleared"?
    Thanks in advance ,
    Ryan
    Edited by: deyi chen on Jun 8, 2011 5:03 AM

    Hi,
    In my scenario system still cancel the invoice which is cleared but should not any accounting impact of canceled invoice
    Even if you try to release manually by VF02 the massage will appear
    Automatic clearing of billing document 12345
    and canc. doc. 17777 not poss.
    If don't want to allow creation of cancel invoice if origin invoice is cleared then do some enhancement.
    Kapil

  • Cancellation Document no accounting doc but cancellation of credit memo

    Hi experts,
    I have cancelled a billing doc then instead of the cancellation document producing an accounting document another cancellation of Credit Memo (S2) was generated. I believe this is SAP standard bug but have anyone of you encountered such scenario?
    Thanks and regards,
    jG

    Hi Sandip,
    Yes this was my expectation but it didn't happen because the accounting didn't post instead another billing document was created in SD with doc type S2 "cancellation with credit memo" which I don't know the logic behind it. So the sequence of my documents are
    1. billing doc
    2. accounting doc of billing doc.
    3. cancellation of billing doc.
    4. cancellation of credit memo.
    If you can see the 4th one instead of another accounting doc this unnecessary cancellation of credit memo doc appeared.

  • How to get - Net amount for accounting doc in the SD doc flow?

    Hi,
    In my report I have to show the net amounts from the Sales doc, invoice and accounting doc, etc.
    I got the FI doc amount from BSEG, however there the gross amount is stored.
    I noticed that in the SD document flow for the accounting document the net amount is shown.
    I tried with the following calculation, however in some cases this doesn't work (eg there is separate tax item in the FI doc):
    "<lwa_bseg>-wrbtr - <lwa_bseg>-wmwst"
    Is there a function module/sap standard code to provide this data?
    Thanks in advance,
    Peter

    when u see the Item Header in SO or Billing , at the Head of Condition table u will get NET amount ?
    are u not maintaining any seperate conditions for this NET amount ?
    have a word with ur functional guys , so he can help u out.
    Regards
    Peram

  • Accounting doc typelink with billing doc type

    Hi,
    I want to see the configuration settings to be done for the accounting document type whenever a Invoice is posted to accounting.Basically if a standard Invoice F2 is posted to accounting then an accounting doc type RV is created.So I would like to know where is the link between the invoice documnet type and accounting document type maintained in the system?

    Hi
    In T code VOFA  in the configuration of the billing type, i think in the control data tab ,there is a field called document type
    This is the field to get the accounting document type
    If that is left blank system takes RV by default
    If you maintain some other accounting doc type in that field, other than RV ,system will pick what you have assigned
    You can test this too
    The Standard  SAP configuration for F2 and many other billing types  that field is maintained blank
    Hence the system picks up RV accounting type automatically
    It is because of the background program ,which runs while billing doc which tells the system to pick RV accounting type ,if that field is left blank ( coding in SAP standard is maintained like that ,to pick RV if that field is left blank)
    Regards
    Raja

  • ALE distribution model - one message type to more than one recipient

    Hello colleagues,
    currently I'm working on an integration project between one SAP system and an e-shop system. The communication is established through IDOCs ( both inbound and outbound ). There is another system ( POS ) which is already integrated
    with SAP via IDOCs also.
       Now I'm facing the following problem regarding distribution of transactional IDOCs ( orders, deliveries, etc. ): when assigning one message type ( for example DESADV - Delivery: Shipping notification ) to more than one external system in ALE distribution model I receive a message alerting that one message type can be send to only one recipient.
    The distribution model is as follows:
    Model Views
       SAP to POS
          SAPDEV ( the SAP system )
             POS ( the external POS system )
                DESADV
       SAP to E-SHOP
          SAPDEV ( the SAP system )
             E-SHOP ( the external e-shop system )
                DESADV
       Well, the system message is clear and I did the obvious: create a complete copy to the original message type and than assign it to the E-SHOP system ( the original message type is already used in integration between SAP and POS ).
    As you can see I have found a workaround already but I think that it comes natural to SAP to communicate with other systems and to exchange same kind of documents to those systems and I can't believe that there isn't a standard solution for situation like this.
    FYI I'm working on SAP ECC 6.0
    Thanks in advance.
    Wish you nice day and successful week ,
    Vladimir

    I believe when ePrint server has received the email, it made the necessary settings and configured the job for printing and then it went for "Reply All" option. So here it cannot send the print job to your personal email ID and the error came up.
    The only option I can think of is add the printer email ID to your email contact list and give it a name like MyPrinter so you can remember easily , just like email contacts are added in Outlook.
    Mark this post as answered so that others can find it useful.
    Say "Thanks" by clicking the Kudos Star in the post that helped you.
    Please mark the post that solves your problem as "Accepted Solution"

  • ALE Distribution Model

    Hi,
    I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : <b>Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.
    </b>
    Next step we delete the model view and created it again but the same error still remains.
    Can anyone help me ???
    Thanks is advance.
    JMMatos

    Hi
    Distribution Model – A model that describes the ALE message flow between logical systems.
    Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPI’s and filters are defined in the distribution model.
    Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
    Sender Logical System – EC1CLNT800
    Receiver Logical System  – SALES
    Message Type – CREMAS
    No filter conditions defined.
    This configuration step allows the installation of core ALE features on which data transfer activity will be based.
    In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
    The distribution model consists of one or more views that you can define
    After creating the distribution model – the model needs to be distributed to the receiver system.
    Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

  • Enable accounting doc posting for PGI consignment 631

    Hi experts,
    Here is my case:
    SD group wants to post Goods Issue (PCI) to customer as consignment stock owned by the company, but they want the system to raise an accounting doc per each transaction (to report that the goods had been sent to the customer; in our regional Accounting Standard, we have this kind of GL account)  through mvt 631 instead of generating accounting doc as it is now.
    MM controls 631 and I didn't figured out how to enable it, please help me!
    Thank you very much
    Best,

    Why you are using 631, if u want a PGI , goods issue cust consignment use movement type 633 . The system will take your Stock CR and COGS + (maintain Gl acct for acct modifier VAX )
    regardzz

  • Control accounting doc. from billing

    Hello,
    for my accountment department, i need that from two positions of one single bill, create two positions in the accounting document. There will be at the same account, but i need two separate postings.
    BILL NR. 1
    POS 10 MATERIAL A 100 EUROS
    POS 20 MATERIAL B 50 EUROS
    ACCOUNTING DOC.
    ITEM 1 CUSTOMER A 150 EUROS
    ITEM 2 ACCOUNT 701000 100 EUROS
    ITEM 3 ACCOUNT 701000 50 EUROS
    ITEM 4 TAX XX EUROS
    This is what i want. Now i get ITEM 2 ACCOUNT 701000 - 150 EUROS. Is it possible to separate the positions?
    Thank you.

    SPRO - IMG - Financial Accounting - Financial Accounting Global Settings - General Ledger Accounting - Business Transactions - Integration - Sales and Distribution - Perform Document Summarization for Sales and Distribution.

  • Restroct billing doc is it doesnot generate accounting doc

    my situation is:
    client does not want to allow sap to save billing doc in vf01 if no accounting doc get generated.
    debajyoti

    Dear,
               You want just the customization in SAP.
                SPRO ---> Sales and Distribution ---> Billing -
    > Billing Documents -
    > Define Billing Types (Select your billing type and go in change mode) -
    > Go in General Control ---> click on posting block(To block automatic transfer of the billing document to accounting, mark the field.).
    Regards,
    Sandip

  • ALE distribution of HR master data to CRM - subtype CELL and MAIL

    Hello,
    Overview/Introduction:
    we are using the ALE distribution of HR master data to CRM. The distribution has already been set up and it is running. We know that the infotype communication (0105) is especially distributing the subtypes 0010 (e-Mail) and 0020 (telephone number). This e-Mail address and the telephone number are stored in the business partner in the CRM system.
    For this infotype 0105 there are also the subtypes CELL (cell phone) and MAIL (e-Mail address). Unfortunately this cell phone number and the mail address (from subtype MAIL) are not stored at the business partner in CRM.
    Our request is on the one hand to store the data from subtype CELL into the field mobile number of the business partner. And on the other hand we want to store the e-mail address of subtype MAIL at the business partner instead of subtype 0010.
    For some reason it seems that these requests canu2019t be setup within SAP standard.
    So we found SAP note 758426 which suggests to use the BAdI HRALEX_INBOUND and the report RH_ENHANCE_BP_TEMPLATE.
    Problem:
    Now the problem is that the BAdI does not get called! The BAdI is active! We tried to set break points -> unfortunately did not stop! And we also implemented an endless loop in the BAdI -> even with this the system did not u2018stopu2019!?
    Any ideas?
    Thank you,
    Roman

    Hi,
    First you need to create a distribution model using transaction BD64 : Edit > Model View > create.
    Then you will need to maintain fields for description and technical name. In partner box you need to enter the source system (HR) and the target system (FI) in the second field. Then you need to assign a message type and filter settings if you need it. You need to create this distribution model in source system (HR).
    After, still in BD64, go to environment > change partner profile or transaction WE20
    Select your target system and enter the corresponding message type ( HRMD_A or HRMD_ABA depends on your scenario) with the correct customizing (receiver port, packet size, idoc type, syntax check and output mode).
    Then please do the same things in your source system using WE20 for your source system and define your inbound parameters (Process code HRMD, processing by function module : use trigger immediately if it is not a production system or else trigger by background program and this case you will need to run report RBDAPP01 to process Idocs).
    Once done, then go back to your model view in your source system (BD64) and go to Environment > generate partner profiles. Then please go to Edit > Model View > distribute
    After all these settings done, it should work.
    Please also check out documentation :
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/82/933b90aa9e11d6b28800508b5d5211/frameset.htm
    Best Regards
    Christine

  • ALE Distribution for Message Type FIDCC2

    Dear all,
    I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :-
    1. Use tcode OB87 to add the Global Company Code, XBJ01.
    2. Use tcode OBV7 to link a dummy (non-existence in sending system)
    Chart of Account to the Global Company code XBJ01.
    3. Use tcode OBB5 to assign the Global Company Code, XBJ01, setup in step 1. to the an existing company code BJ01.
    4. Use tcode BD64 to setup a distribution with message type FIDCC2, and
    filter with value XBJ01.
    5. Create an FI document using tcode FB01 with company code BJ01.
    6. IDOC is created successfully with message type FIDCC2.
    Is there above steps correct? As there are times I receive an error message when trying to do a PGI with company code other than BJ01 "F1302 No cross-system company code is defined for company code TR01".
    Another question is, with setting up of FIDCC2 with ALE distribution, any transaction in SAP that will generate a FI document will have IDOC created, right?
    Thank you.
    Best Regards
    Chee Hean

    I don't know if you still have this problem but my team and I faced a similar issue in production. Due to a project we're handling, a tool that we are executing requested us to create a Distribution Model based on FIDCC2. This stuck hundreds of thousands of FI Document. Actually, for any FI document the system generated an FIDCC2 and it's not possible to reuse those IDocs because the FIDCC2 Message Type has a structure completely different from FIDCMT (the original message that the system should generate). We identified all the IDoc that should be generated and re-create the Idocs in the target system and the Idocs we posted correctly. We change the FIDCC2 IDocs status to 62 or 32 (depending if inbound system or outbound system). I recommend to investigate about this message type before use it. This Message Type is stronger than any other message type so it must be filter perfectly otherwise, for sure, problems will appear.
    Regards,
    Hugo

  • Multiple account assignment switching between distribution indicators not working for service

    Hi Gurus,
    Account assignment distribution function not working post ECC6 patching activity
    we have recently completed ECC6 patching actvity and we are facing issues on processing multiple account assignment in service.
    we create Purhcase order with single account assignment and will process service with Multiple account assignment selecting distribution on qty or percentage basis till patching functionality works fine post patching we are facing issue when we are selecting distribution indicator system provides an error message switching between distribution indicator is not allowed when we continue system ask to enter in case of multiple account assignment select the distribution indicator. could you please suggest me on the issue.
    Thanks in advance.

    we have found a SAP note
    1915000 - SE685 - Switching between distribution indicators is not allowed
    This is now standard behavior.

  • ALE distribution error - 0 communication IDOC

    Hello,
    We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
    Anirudh

    hi,
    ani,
    u check this,
    If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
    Or
    You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
    Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
    You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
    You can set the indicator in Customizing Document Management System  Define document type  Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
    You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
    You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
    Information about object links are distributed through IDoc type DOLMAS01.
    The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
    You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System  Define document type  Define transport of originals for ALE. You can control distribution with various criteria.
    You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
    You can process the status for the desired objects.
    1.     Select in Customizing Cross Applications Components  Distribution (ALE)  Standard ALE Business Processes  Logistics  Master Data Distribution  Integrated Distributed PDM Solution (ID PDM)  Object status (for example, Define BOM status).
    2.     Process the indicator Distribution lock
    ben

  • ALE Distribution Lock

    Hi all,
    can anybody tell me what is ALE Distribution Lock ...
    regards
    sreedhar rusuma

    Here is the documentation for ALE distribution lock
    You determine whether you want an object, for example, a document, to be distributed via ALE into other systems by setting the status, for example, document status.
    The indicator Distribution lock prevents an object, for example, a document, from being transported into an ALE system.
    A change pointer is always set for the distribution lock during distribution even when sending within the ID PDM Solution. The system automatically creates a change indicator and a Master IDoc for distribution when you change a distribution relevant field, for example, status, for a message type, such as DOCMAS for documents.
    It is possible to ignore the distribution lock when you send objects manually. In this case, the entire object is transported into the ALE system according to the distribution model.
    Manual distribution is only of importance for change master records within the ID PDM system.
    See also:
    Change Master Record : IDoc Type ECMMAS01
    Objects
    You can control the ALE distribution for the following objects within ID PDM via the status:
    Material
    Characteristic
    Class
    BOM (material BOM, document structure)
    Document
    Object dependencies
    Change master record
    Activities
    You can process the status for the desired objects.
    1.  Select in Customizing Cross Applications Components --> Distribution (ALE) -->Standard ALE Business Processes --> Logistics --> Master Data Distribution --> Integrated Distributed PDM Solution (ID PDM) --> Object status (for example, Define BOM status).
    2.  Process the indicator Distribution lock

Maybe you are looking for