Dear Community,
As part of our travel configuration, we are using the “BAR Accounting Name” field to control profile behavior in the GDS (Amadeus).
In our testing and experience, the following behaviors appear to be supported (but undocumented):
Prefixing with ^ merges the company profile with the user profile
Prefixing with * appears to move or create the user-level profile only
Adding multiple values separated by a comma (e.g. ^VIECO315Y-ORG,VIECO315Y-ORG) appears to have undefined behavior, and does not produce consistent results
We could not find any official SAP Concur documentation that describes the correct usage or expected results when using these options.
Is there official technical documentation or a best practice guide for the “BAR Accounting Name” field, including:
The behavior of ^, *, and comma-separated values
Expected results when combining or merging profiles
Behavior differences between guest bookings and registered users
What is the recommended method to dynamically control whether a company profile is moved to the GDS for:
Are there alternative approaches (e.g. via API, rules engine, or finishing templates) to dynamically assign the BAR/STAR/Worldfile per booking context?
We have observed that using ^VIECO315Y-[ORG_UNIT_NAME] results in correct company profile transmission for registered employees, but not for guest travelers.
Conversely, using VIECO315Y-[ORG_UNIT_NAME] works for guest profiles, but breaks GDS profile transfers for registered users.
We are looking for a scalable, documented solution that works reliably for both cases.
Thank you for your support!
Kathi and Veronika
