topic Re: Substitution does not trigger when posting through FB01 in Application Development and Automation Discussions

Substitution does not trigger when posting through FB01

Former Member — Mon, 04 Jan 2016 09:28:52 GMT

Hi all,

My requirement is when user post through tcode FB01 ,the posting date should change to first date of next month if posting period is closed.

i am trying to achieve it through Substitution but the substitution does not trigger when posting date is in closed period as it throws standard error .

Please help.

Re: Substitution does not trigger when posting through FB01

RaymondGiuseppi — Mon, 04 Jan 2016 13:17:20 GMT

You could use BAdI FI_HEADER_SUB_1300 to prepare default data for screen.

Alas for your exact requirement, I fear that the period check is executed too early in a PAI module of screen dynpro, so you may be required to find some (implicit) enhancement before call of FI_PERIOD_CHECK.

Regards,

Raymond

Re: Substitution does not trigger when posting through FB01

Former Member — Tue, 05 Jan 2016 09:36:36 GMT

Thank you for your help Raymond but i don't think BADI or implicit enhancement would be good option as i need to change posting date from multiple Transaction codes.its like if posting is done through any module (SD MM, FICO) the posting date should change to the first of the following month if the posting date is within closed period.

Anyways for now my functional said that in transaction code OB52 if we maintain the whole year open for account type + then it will trigger the substitution then on each account type (K,D,S,A) we need to closed the period .

Re: Substitution does not trigger when posting through FB01

Former Member — Tue, 05 Jan 2016 11:06:24 GMT

Did you 'activate' the substitution? I remember I had to change something in a (customizing) table: tc OBBH

Re: Substitution does not trigger when posting through FB01

Former Member — Wed, 06 Jan 2016 12:50:24 GMT

Thanks Zhou..But the substitution is very much active because when i trigger through MIRO and try to change the posting date it works completely fine.