Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What must I consider when adding a new user field (=> user field was not previously used) in a migration without document splitting?

0
Posted

What must I consider when adding a new user field (=> user field was not previously used) in a migration without document splitting?

0

– If you want to fill the field for at least the migration of documents in phase 1 and save the field in the totals table, it must be available at coding block level (=> CI_COBL) as of the migration date, and a derivation logic must be implemented (by the customer). – For the balance carryforward of G/L accounts not managed on an open item basis in phase 0, you can use the standard BAdI to subsequently add a new user field (with implementation by the customer). – For open items in phase 0, there is no standard option (for example, BAdI or program) as of January 2008 to subsequently add the user field.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123