Kevin, et al, Since you are talking INBOUND ANSI, DO NOT REMOVE ANY RECORDS IN THE ASNI in the Oracle e-Commerce Gateway for inbound transactions. Just don't define them in the Translator's data map if you do not need them.
You would remove records for OUTBOUND so you don't get a lot of blank records on the multitude of Attributes (Descriptive Flexfields) columns. Even then, remove ONLY full records, DO NOT remove columns in the middle of the record just to avoid any Seed Data Reconciliation problems if Oracle changes a record. Having unused fields along a record that you are using does no harm. They will have data that you will not map. Back to the inbound tran record layouts in ECG. Though the ECG Tran File Definition (record layout) may have 50 records (for example), and you need ONLY 15 of the records, you just need to map and create the 15 records that you have data to put into the Open Interface Tables. Unless there is required data on a given record, the Gateway is not looking for all records that are defined in its record layout. It will look for the first record that starts a data level like the 1000 record to start the header data (maybe 2000 for the next level). Record 0010 is required to start a single transaction. Other than those, only certain columns may be required. You are NOT required to define those 35 not used records in your Translator's data map. It is important that the Gateway and the Translators layouts agree on field lengths and record numbers on records that you do write to the file. That is all. Use your Translator's data map report for the official document of which records you are using. You do not need to rely on the longer ECG report since it will have records that you did not use. If you want the Gateway's report to really indicate which records you are using, then you may want to remove full records. But don't remove records for any other reason such as thinking it required that record in the data map because you see it defined in the ECG. Make sense? Call me if you want to discuss this further. Glad to help you on the implemention on this product. Bonnie Shebat Williams 408 230 6635 Former Oracle Product Manager on the development of the E-Commerce Gateway -----Original Message----- From: Susan Stecklair <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]; [email protected] Sent: Sat, 29 Oct 2005 15:17:21 -0700 Subject: [EDI-L] Oracle 11i EC Gateway Kevin - I'm replying to your questions about the design and archectecture of your inbound ASN using Oracle 11i. It appears to me that you are in the Unit Testing Phase. I would not begin deleting or deactivating records at this stage. 1). Oracle 11i: My recommendation would be to add a "Post Production Clean-up" to your Project Plan AFTER the implementation of 5 to 10 of your large suppliers for documentation & maintenance ease. Then prune the records accordingly, and update your documentation. As a control process, I've kept an EXCEL spreadsheet of all the records/elements & their attibutes from Interface Record & if it is not used just note it. In many cases, if you are working for the hub, there will only be minor changes to the business requirements as you deploy to other suppliers. 2). Adding all these records to your Gentran layout & map is really a call that the EDI-L group cannot make for you. If you are in an environment that has a rigid and time intensive change control process, then add all the records/elements. It is about a 2 day effort. You can generate a report from GENTRAN to validate your layout. If not, add the records you have analyzed you require only and modifiy the map as changes occur. Inform your management, that you will need to perform a "GAP analysis" for incrementatal implementations if you anticipate different business requirements for additional suppliers. Also, Gentran offers templates for the Oracle extensions. You might check to see if your company purchased them with the translator. It saves time in input & error correction. Hope this helps. Regards, Susan Stecklair Hi: We are implementing ASNI (Advanced Shipment Notice) 856 EDI using Oracle E-commerce Gateway technology within our Oracle 11i Business Suite application. We found that there are more than 600 columns defined for ASNI (IN: Ship Notice/Manifest (856/DESADV) for Header, Line, Line Detail, Serial Details, RCV Serial Details and RCV Lot Details levels. However, we only plan to use a subset (roughly 100 columns) of those 600 columns for our ASNI EDI based on our agreement with supplier. Since we also need create a mapping file using our EDI Translator software (We are using GENTRAN) for ASNI, we run into 2 options here: Option 1: Disable (by setting record number, position and length to blank) all non-used columns (about 600 -100 = 500 columns) in Data File Record Layout definition for ASNI transaction of Oracle 11i first. Then, create mapping for only those columns that are being used. Option 2: Don't disable any columns in Data File Record Layout definition of Oracle 11i. Then, create mapping for all columns (~600 columns) in our EDI translotor software. As you can see, option 1 is easier to implement comparing to option 2. My question is: Which way (option 1 and 2) is a more practical when people implement EDI within Oracle 11i when there are lots of columns are not used in Interface Data File Record Layout for some transaction? Thanks! Kevin __________________________ -- Susan Stecklair URL: www.ecommerce-inc.com Phone: 408.996.7492 Email: [EMAIL PROTECTED] [Non-text portions of this message have been removed] ------------------------ Yahoo! Groups Sponsor . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/OIFolB/TM --------------------------------------------------------------------~-> . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
