on 09-07-2006 6:04 AM
What is the advantage of linking "usage dependency" in a software component version? I'm aware that this process automatically includes objects from other s/w component. But how this is used in real life integration? An example would help in understanding better. To stress the question, lets assume component_B (contains SAP IDOCS MATMAS, CREMAS) is included as "basis components [result of usage dependency]" in components C to Z. If a segment is changed in MATMAS IDOC in source SAP system what are the steps to import the new segment into XI IR, SLD for components C to Z. Is it a complete redo or shortcut exists! Thanks in advance.
Hi,
have a look at my weblog to understand:
/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.