Balance Rollup (with ALE-Idocs) as well as normal transactions
Hi,
We have two Systems, say A and B. The System B is a centralized system and has many Company Codes. Company Code 1000 operates out of System A. In order to facilitate consolidation, the Company Code is also created in System B and there is a Balance Rollup (using Idoc FIDCMT) from System A to System B.
In this scenario, what happens if an accounting entry is directly posted in Company Code 1000 in System B? In other words, how would the IDoc determine the delta amount to be posted when the rollup happens after such a direct posting?
Example:
System A. GL Account 100102 has a Dr. balance of I00.
Balance rollup happens and this automatically creates the Dr. balance of 100 for the same GL Account in Comp Code 1000 in System B as well.
Subsequently, I pass an entry debiting Gl Account 100102 with 20 in System A.
I pass another entry in the same GL Account in Co Code 1000 in System B debiting it for 5.
Now, I execute the rollup.
The total new balance for this GL Account in System A is 120.
How and what will the Idoc determine as the delta to be posted? 20 (120-100) or 15 (120-105)
If it is 20, on what basis will the system not consider the additional debit of 5 directly done in System B?
Thanks and Regards
Sriram Sampath
You'd need to determine the b/f then apply it against the
transaction records when they are pulled for a date range. So if
the date range is
Feb 1st, 2009 -> Feb 28th, 2009
You'd need to also get the previous balance in a separate
query, then use it to correctly display the running balance when
you output the date range.
I suppose a simpler way involving a little more DB work (and
possibly lots of coding) is to store the current balance as well
with each transaction; then when performing a date range you'd have
the balance as well and not have to calculate it on the fly.
Similar Messages
-
PLEASE HELP ME WITH ALE,IDOCS,EDI
Hey SAP Experts
can you guys help me out with <b>ALE,IDOCS,EDI,SOL </b><b>MAN</b> materials please .
mail them to [email protected]
Thanks a lot in Advance
sd learnerHi,
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
For Solution Manager, please check links.
http://www.sap.com/services/pdf/BWP_SB_SAP_Solution_Manager.pdf
http://service.sap.com/solutionmanager
Regards,
Ferry Lianto
Please reward points if helpful. -
Data migration with ALE/Idoc
Hello .
I want to migrate data between two SAP system using ALE / IDOC, and I want to know the settings to make on each system (source and target).
Does someone has an idea?
Thank you allOutbound Settings
Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
u2022 Go to Define Logical System (See the figure)
u2022 Define a new logical system to identify the local system and save it
u2022 Now, go to Assign Client to Logical System (See the figure)
u2022 Add a new entry
u2022 Specify the client, previously created logical system and other attributes
u2022 Save the entry
u2022 Define a new logical system to identify the partner system and save it
Maintain RFC Destinations u2013 Transaction SM59
u2022 Create a new RFC destination for R/3 type connection
u2022 Specify the target host on Technical settings tab
u2022 Provide the Logon credentials on the Logon/Security tab
u2022 Save the settings
u2022 To verify the settings, Click on Test connection or Remote logon
Define Ports u2013 Transaction WE21
u2022 We need to define a tRFC port for the partner system
u2022 Click on Transactional RFC node
u2022 Create a new port
u2022 Provide a description
u2022 Specify the name of the target RFC destination
u2022 Save the object
Maintain Distribution Model u2013 Transaction BD64
u2022 Click on Change
u2022 Create a new model view
u2022 Provide a Short text and Technical name to the model view
u2022 Add message type
u2022 Specify sender and receiver systems
u2022 Also, specify the message type that we created previously
u2022 Save the Distribution model
Generate/Create Partner Profile u2013 Transactions BD82/WE20
u2022 To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
o Otherwise, you may use transaction WE20 to create a partner profile
u2022 On selection screen, specify the model view, target system and execute
u2022 The result log will be displayed on the next screen
u2022 To verify the partner profile go to WE20
u2022 Check the partner profile for the target system
Distribute Model View u2013 Transaction BD64
u2022 Select the Model View
u2022 Go to menu path Edit -> Model View -> Distribute
u2022 Result log will be displayed on the next screen
Inbound Settings
u2022 Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022 Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022 Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed)
u2022 Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed)
u2022 Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed)
u2022 Assign Function Module to Logical message u2013 Transaction WE57
o Create a new entry
o Specify name of the Function Module
o Also, specify Type as F, Basic IDoc type , Message type and Direction as 2 (Inbound)
o Save the entry
u2022 Define Input method for Inbound Function Module u2013 Transaction BD51
o Create a new entry
o Provide Function Module name
o Specify the Input method as 2
o Save the entry
u2022 Create a Process Code u2013 Transaction WE42
o Create a new Process Code
o Select Processing with ALE Service
o Choose Processing type as Processing by function module
o Save the entry
o On the next screen, select your function module from the list
o Save the changes
o Now you will be taken to the next screen
o Double-click on Logical message
o In the Assignment to logical message, specify the message type
o Save the changes -
How to start with ALE and Idocs
Hi,
I want to start with ALE/Idocs, Could you please guide me from where should I get the docs for that.
A lot of thanks in AdvanceHi Nitin ,
Pls go through the book by Arvind Nagpal , one of the best books that no one should miss.
Have a look at this site as well
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/
Check this thread, where you have step by step creation of IDOCs:
idocs
Check these links, where you get the complete information on IDOCs:
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
Regards,
Vvieks -
Ale / Idoc Customer master
hi all,
i am working with ale/idoc .
from one client i am sending customer master data using DEBMAS
I have checked in IDOC
for contact person
it is not picking fax number and email
and telephone number it is picking from KNA1 table
reagrds,
mohd.Hi,
the data you try to distribute, even if related to customer master data, does not belong to it.
It belongs to the Business Address Services (BAS).
As a result, to distribute it you need to distribute ADR*MAS idocs types too.
According to the fields you try to distribute, idocs types ADR2MAS and ADR3MAS are definitively necessary.
You should look at [note 384462|https://service.sap.com/sap/support/notes/384462] and [note 306275 - Transferring address data|https://service.sap.com/sap/support/notes/306275].
Best regards
Alain -
Hi Experts,
I have a requirement for integration of SAP HR system with the CRM system and pull in few infotypes from HR to CRM. So, please suggest me which approach is the best practice for the integration process. I suggested my client with ALE/IDOC as they have an existing ALE and proposed them creating a new distribution model view for the infotype we need to enhance. But they were asking me to go with RFC approach as they face some issues in data replication. Also i wanna know about the reliability of both the approach after integration. How safe is the implemented approach good in support and future management? Please clarify me on this one and help me out.
Regards,
Arunmozhivarman.Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi. -
Urgent: Application Object Type for ALE IDoc
Hi All,
I am struggling with ALE IDoc, I just wanted to know that is it mandatory to create Application Object Type when i have created my own message type, Idoc type, segment type and Function Module. I am Getting an error while excuting transaction we42( Maintaining Process code)
Error: Application Object Type is not planned.
Please Help with this. i don't have any requirement of filtering or serialisation, so still do i need to create these application objects.
Useful ans will be rewarded.
ThanxHi,
Yes u need to have the assignment of Object type as ur extending the IDOC.
Check the steps below:
TCode- BD95.
Create ALE object type Z... with table name EKKO and Field name -BSART
Step2:
Tcode- BD59 Assignment of Object type to Message
Give the message type ORDERS.
Assign the object type Z........ to segment type E1EDK01 with field BSART.
Regards
Kannaiah -
what is the tcode for assigning message types and inbound function module in ale
please reply me
thanks & regards,
hari priyaHi Hari,
Steps relate to idoc
Creation of IDoc
To Create Idoc we need to follow these steps:
1)Create Segment ( WE31)
2)Create Idoc Type ( WE30)
3)Create Message Type ( WE81)
4)Assign Idoc Type to Message Type ( WE82)
Creating a Segment
a)Go to transaction code WE31
b)Enter the name for your segment type and click on the Create icon
c)Type the short text
d)Enter the variable names and data elements
e)Save it and go back
f)Go to Edit -> Set Release
g)Follow steps to create more number of segments
Create IDOC Type
a)Go to transaction code WE30
b)Enter the Object Name, select Basic type and click Create icon
c)Select the create new option and enter a description for your basic IDOC type and press enter
d)Select the IDOC Name and click Create icon
e)The system prompts us to enter a segment type and its attributes
f)Choose the appropriate values and press Enter
g)The system transfers the name of the segment type to the IDOC editor.
h)Follow these steps to add more number of segments to Parent or as Parent-child relation
i)Save it and go back
j)Go to Edit -> Set release
Create Message Type
a)Go to transaction code WE81
b)Change the details from Display mode to Change mode
c)After selection, the system will give this message The table is cross-client (see d)Help for further info). Press Enter
e)Click New Entries to create new Message Type
f)Fill details
g)Save it and go back
Assign Message Type to IDoc Type
a)Go to transaction code WE82
b)Change the details from Display mode to Change mode
c)After selection, the system will give this message The table is cross-client (see d)Help for further info). Press Enter.
e)Click New Entries to create new Message Type.
f)Fill details
g)Save it and go back
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
REWARD IF USEFULL
Thanks -
Any having the Experiance with message type UTILMD and REQDOC in ALE Idoc
Hi experts ,
I am working with SAP ISU ,in ALE Idoc message types UTILMD and REQDOC,
ver 3.0 and 4.0 ,I got the almost all necessary details of UTILMD MESSAGE TYPE..but REQDOC is pending.If any one having the format of REQDOC segments and objectypes in SAP ISU please send it to me it will be very helpful to me .
Regards
SarathThak you for the responce,
Hai Naveen,But i dont have message type or structure for REQDOC ver 3 or 4 .in SAP .do you have that structure for REQDOC in the transaction we30 .if so please send me its mainly used for SAP ISU .
regards
sarath -
ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3
Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
StevenHi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi. -
File to convert to IDOC from bus.service failes with ALE#LI
Hello,
we habe implemented a scenario:
Non SAP system sends a structure to be uploaded to an R/3 system as IDOC.
All config looks fine.
We followed this description:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
So system is identified in adapter specific data as log.sys. LS test1 .
But we have this error:
Unable to convert partner abc / ALE#LI into an IDOC partner (message in german, only translated)!
Does anybody has an idea what is wrong?
Is it necessary to have the log.sys name in the message e.g. in SNDPRN?
Here we have after mapping:
<SNDPOR>testABC</SNDPOR>
<SNDPRT>LI</SNDPRT>
Best regards
Dirk
Message was edited by: Dirk Meinhard
Message was edited by: Dirk MeinhardHi Nimrod,
looks like I am not totally wrong here, but working together with externals who provide the outbound side is not really easy for testing.
Here is the EDI_DC-40 segment AFTER the Mapping, so the XML for the inbound IDOC:
- <PORDCR05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>010</MANDT>
<DIRECT>1</DIRECT>
<IDOCTYP>PORDCR05</IDOCTYP>
<MESTYP>PORDCR</MESTYP>
<SNDPOR>A000000039</SNDPOR>
<SNDPRT>LI</SNDPRT>
<SNDPRN>0005354880</SNDPRN>
<RCVPOR>SAPK10</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>LOG10</RCVPRN>
</EDI_DC40>
Here is the error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Aufruf eines Adapters
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>Partner_ABC</SAP:P1>
<SAP:P2>ALE#LI</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Sender XI Party Partner_ABC / ALE#LI / could not be converted to IDoc Partner </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In my opinion we have to implement in WE20 of receiver R/3 system a partner LI with this number A000000039 from the EDI DC 40 segment? And we need to add it as identifier LOGICAL with ALE#LI and this number A000000039.
R/3 consultant says he cannot do this in the receiver R/3 system because the sender is no supplier in his system!
regards
Dirk -
Can we go with ALE configuration instead of receiver idoc adapter at target
Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj -
Integrating SAP CRM with the SAP HR module using ALE/IDOC
Hi,
We replicated HR data(employee and position) from SAP HR to SAP CRM system using ALE/IDOC.
Here I have one question,If I change the position to the employee in CRM system,will changes happen in SAP HR system automatically? or Delta changes will haapen? If yes pl explain.
Using change pointers master data changes flowsfrom SAP HR to SAP CRM .
TIA.
PV.Hi
To integrate... between those systems
first of all u have to create message type to tose fields with t code bd52.
then activate that massege type in bd50.
and after that one u have to activate chaneg pointers globally with bd61.
if u did these thigns if u made any chnegs to those fileds that witll be reflected in the next system
Regards,
Prasad. -
ALE IDOC with T-code :IE01
How is an ALE IDOC generated when an equipment is created with T-code :IE01
Hi K.R.,
First of all you need to check if everyting works fine.
For this specific IDoc you can check table T705Z with KANAL='2' and AKTIO='4' and with DATUM=<Date of receiving IDoc>. You can also use UZEIT as a filter here.
Why?
At the moment this IDoc (CONF21) comes inbound to SAP, through the process code CON2 it actually must start function module KK2A_GET_DATA_FROM_IDOC. This places the entry and you can then see that your function has been called.
Secondly inside function module KK2A_GET_DATA_FROM_IDOC the process for updating is started in a parallel (asynchronous) process. Actually function module PROCESS_CC2_MESSAGES_PARALLEL is triggered as a background task that controls its own parallel processing. On its turn this calls the logic in function module PLANT_DATA_ANALYZE_PARALLEL and therein the function module PROCESS_CC234_MESSAGES.
With these mentioned function modules a table is preserved (named ET_PROT) and this table contains (internally) any message, so also error message text.
Unfortunately you are not able to get to this internal table if the proces is running in the background.
Now when SAP calls the parallel process (in background), programcontrol is returned immediately. So function module KK2A_GET_DATA_FROM_IDOC can then finish. Finishing here without setting any error status will lead to final status 53 for the inbound IDoc.
And as you can imagine, it does NOT wait for the result of the background process. Therefore status 53 represents only the fact that function module KK2A_GET_DATA_FROM_IDOC has runned without errors. It does not report errors possibly occuring in PROCESS_CC2_MESSAGES_PARALLEL.
Now how is this then to be solved?
You need to create your own data for running the above mention logic, preferrably based on failed IDoc data and then debug the whole thing (to find the error).
Hope this helps you a bit on your way,
Regards,
Rob. -
ALE/IDOC interview q's with answers(urgent)
Hi folks,
I want ALE/IDOC q's and answers .I have gathered some ,but still i want more...Please send as soon as possible.
Regards,
nagarajHi,
Remember all the following TCodes:
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDoc in Database
WE10 Search for IDoc in Archive
WE12 Test Modified Inbound File
WE14 Test Outbound Processing
WE15 Test Outbound Processing from MC
WE16 Test Inbound File
WE17 Test Status File
WE18 Generate Status File
WE19 Test tool
WE20 Partner profiles
WE21 Port definition
WE23 Verification of IDoc processing
WE24 Default values outbound parameter
WE27 Default value inbound parameter
WE30 Development IDoc Type
WE31 Development IDoc Segment
WE32 Development IDoc View
WE33 Value tables for IDoc documentation
WE34 Object for Display of XML IDocs
WE40 System process codes
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and Checks
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 IDoc administration
WE47 Status Maintenance
WE48 Inbound process codes: Texts
WE49 Inbound process codes: Change texts
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE52 Outbound process codes: Texts
WE53 Outbound process codes: Change texts
WE54 FMs for changing file names
WE55 Function Module for Path Names
WE56 Status process codes
WE57 Assignment Messages for Appl. Objs
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Parser for IDoc types and rec.types
WE64 Documentation message types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE81 Logical message types
WE82 Assignment Messages for IDoc Type
WE84 Assignment of IDoc and appl. fields
OYSN Number Ranges for IDOC
sm59 Set up the RFC Destination
If you want You can further Refer the Text Book By: Aravind & Nagapal.
It is very useful.
Regards,
Anji
Maybe you are looking for
-
How do iI close my apps I have over 20 open and cant close em down
How do I close my Apps I have over 20 open and cant close em down
-
Error in char. Info Object
I have created the char . info object and in attributes gave the same char. and made it as navigational attribute. when i am trying to activate the info objecty i am getting the error "Name of the Characteristic is Reserved". Can nyone plz let me
-
Screen for 'Additional Data B' of VA01
Hi folks, i want to add one field cusomer no in 'Additional Data B' tab of VA01. can anyone tell me the screen number for 'Additional Data B' of VA01 & the complete process of creating the field & validating the VBAP table? Points will be awarded. R
-
mandatory update for adobe AIR get error message #16820
-
Query for tabstrip & Table control
Hi, I have never used tabstrip & Table controls.I have worked extensively on ALV & Smartforms.I am finding it difficult to understand the steps now,after a long gap of returning to tabstrips & table control.I have all the standard programs for the s