on 06-30-2014 11:45 AM
Hi Folks!
Being new to AIF I'm currently in the information gathering phase for myself and colleagues as we are starting to think about implementing interfaces with the help of this toolbox. I already found and read (or at least skimmed!) through various of your discussions as well as the very helpful blog posts from Verena, Michal and Andrey.
One of the first things we want to do - before we really get started for real - is to come up with some feasible naming conventions for the various customizable bits and pieces like
We also have some general questions:
Searching SCN for "naming convention aif" didn't find anything related and while scrolling through the discussion forum I also didn't see any titles which might go into this direction. In order for us to not re-invent the wheel - or to start off in the wrong direction - I'm hoping to get some helpful pointers from you.
Thanks much for any feedback you have!
Cheers from Germany
Baerbel
From my limited experience:
We also have some general questions:
Good luck.. keep a "lessons learned" document and don't be afraid to create a blog based on it.
Regards,
Robert Phelan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Folks,
thanks for your feedback thus far (more is certainly welcome!).
Today, we made a decision to have our namespaces start with a "Z" followed by the process or application it is created for. In most cases, this will either be an internally defined short process-name or an SAP-module.
For the interface-name we'll wait with a final decision until we actually have more experience with AIF but we already decided that it won't need to start with a "Z" as an interface cannot exist without the namespace and that will start with a "Z".
Another open question is how best to fill the version. As this is a character field, I'm wondering if it actually has to be filled with numerical values (as seen in some traning material) or if it could also be used to set up different definitions as needed e.g. by company code or country. If it's to be filled with numerical values only, than these should - in my opinion - always use the complete length with leading zeroes and be incremented in steps of 10 (e.g. 00010, 00020...00100..). Without the leading zeroes, the sort-order would be out-of-whack as soon as you have more versions (e.g. 1, 10, 2, 3...)
The other general thing we have decided is to centrally control the naming of these AIF-organisational entities and to not make this a "free-for-all".
Any thoughts on this?
Thanks and Cheers
Baerbel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bärbel Winkler,
Could you kindly share the naming convention you have come up with. We are in the process of creating a naming convention document for SAP AIF objects.
Thanks,
Sudhansu
Hi Sudhansu,
this is what we got thus far - which isn't all that much:
Namespace | 06 | Z* | The 5 freely available characters should either denote the application/project the interface is for or the SAP-process area it belongs to. |
Interface | 10 | * | Descriptive name for the interface |
Version | 05 | NNNNN | Character field - numerical content needs to be numbered in steps of 10 and have leading zeros |
Raw Structure | 30 | Z* | tbd |
SAP Structure | 30 | Z* | tbd |
This is however bound to evolve as we are still in the process to implement our first processes via AIF.
Hope this helps at least a bit!
Cheers
Baerbel
Hi Bärbel,
Your question is very good. We had the same and decided for following own approach:
We also have some general questions:
Best wishes
Christoph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.