I've created a new session and I want to copy this session and it's components into the 'live' vrc. So I run ttiex1280m000 and complete the screen as attached.

When I view my dump.l file I notice that there are a lot more components than what I expected. Ones that seem totally irrelevant to my session. e.g. labels for tiitm001, which have nothing to do with my session. Table defs, again for tables not related to my new session.

This is something I have noticed before when running exports based on sessions and I've usually exported the specific components.

My worry is that I'll start overwriting components that I shouldn't be.

Can somebody please explain why I see non session related components. I would only expect to see items that I have created whilst developing my session.

Thanks

PJ

Use Form 3 to specify which specific components you want to include.

See online help for field Based Sessions in Form 1

Hope this helps.

PJ,

is your liv0 VRC directly under your tst0 VRC?

alejandro - I want to avoid using form 3 if I can help it as I've made changes to domains and labels. Whilst I can probably remember which ones they are if they are not in a range I'll have to run the export a number of times.

Help on 'Export based on session' says that the system will also deliver the data dictionary needed by the session.

So it's saying my tdsls session needs components from tiitm, tdilc?? The only reference my session has to another table is via the pack slip number in table tdsls045.

pat - Yes liv0 is directly under the tst0. (My tst0 vrc is derived from my liv0 vrc)

Regards

PJ

In my experience, exporting by session ALWAYS exports more (often much more) than I actually changed and/or need. So, I always track my changes using the customization administration features. I used to then individually list the components on form 3. However, we recently created a tool in house to automatically take the data from the customization tables and use ttiexdeliverp to export exactly what we need. There is a recent post regarding ttiexdeliverp that might be useful. I believe gfasbender sells something like that, too.

I agree with Ed: Always use CA to create an explicit list and a customization to create input to tteixdeliverp to export based on the list. Even without a customization you can create a simple vi input file for ttiexdeliverp. We've been doing this successfully for 4 years with Baan 4 & 5.

Could somebody please give me a quick rundown on how to use CA?

Thanks

PJ

Cursory but effective help text for sessions in Tools/Appli Devel/
Custom Admin. Follow thread from project to project part to customization part. CA is just a way of organizing lists of components. You (customer) define what each project & part mean to your organization. CA tables can be used by custom sessions to create ANSII file for input to ttiexdeliverp to actually do the Export DD.