Many a times it is found that the developers simply take up the maps without analyzing the provided application layout and FMD. In the midst of the mapping process lot many issues crops up and leads to utter confusion and pushing us for remapping and client’s agony. Hence to avoid any complicacy we should be serious enough to study application layout.
Application Layout plays an important role so far as EDI mapping is concerned. In case of Inbound translation, X12 or EDIFACT data is being parsed by the translator and populates the application layout following the map rule as mentioned in the FMD. On the other hand, in case of outbound translation, X12 or EDIFACT data file is generated from application data following the mapping rule as mentioned in the FMD. We have to remember that if we don’t understand the structure of application layout properly, then mapping would be wrong and generated output will not be as per requirement.
There are various types of Application Layouts. It might be in flat file structure or in XML layout. In the flat file structure, data can be displayed in delimited style or at a fixed offset. In SAP application layout for various business documents, we find records of fixed length and the specific fields for specific purpose. We have to study field types, length and alignments etc so that while generating outbound maps we know about the look and feel of the expected output. Like we have seen while studying the X12 data structure, they follow a particular data hierarchy, maximum/ minimum occurrence of Segments and looping structure, here also in SAP application layout there are many such rules and regulations. Think of a scenario where we have to generate an X12 in version 4010 where a particular Header segment can come for maximum of 6 times. While studying the application layout and provided test data we found that particular record is coming for 10 times, while the EDI record which is to be generated has a maximum limit of 6 times. Now if we try to translate the map with this sort of test data then an error will occur. We are in a fix! As there are many possible way outs but the most feasible option is to look for such a version where the target segments may come for desired numbers. Changing of source application layout structure is certainly not a wise proposition and if at all required then we have to inform the relevant agencies.
Different EDI mapping tools handle application layout in different ways. We have to be well conversant about application layout handling process and require intensive tool-based training. Here again I must reiterate that if we do not understand the structural intricacy of application layout, super tool based knowledge will not be helpful.
Just to have a visual impression of how an application layout looks like, I am giving a few screen shots :
Visit us at www.crossroadtechnoloies.in
Sunday, December 7, 2008
Subscribe to:
Post Comments (Atom)
One more thing I would add here is:
ReplyDeleteYou should also verify that the test file (application file for Outbound map) is in sync with the application layout. Sometimes it may happen that the layout has some record with maximum occurence as X & the application file has that record coming up > X. Thus, this file is in error. The records may be sometimes misplaced by the client i.e in the wrong groups.
Thanks
Arpit
The above screens look very familier :-)
ReplyDeleteGreat article! It is a definite necessity to know the layout of the application. Currently my company is using the IBM Sterling Integrator software and I know that thing inside and out.
ReplyDeleteHello there ! EDI tools is the primary step towards the achievement of such goals and objectives. Thanks for sharing this valuable post.
ReplyDeleteedi service provider.