Page 1 of 1
BTE 00001030 problem
Posted: Wed Apr 18, 2007 9:06 am
we have customized the 00001030 business transaction event (BTE) to start a particular function module.
When we use transaction FB01 to post a financial document, the function module is called.
When we use the relevant bapi BAPI_ACC_INVOICE_RECEIPT_POST, the function module is not called.
So my question is, are the fi badi's triggering bte's ?
And, is there a tool to see whether the 00001030 is really used ?
Posted: Wed Oct 10, 2007 2:21 pm
i'm trying to build a custom bte to do a substitution on Payment block (ggb1 doens't do this field) I can't figure how to get the one I want turned on. I tried using 1140 but it doens't change bseg i thought 1160 would work but can't seem to get it to that call point.
do you know how to determine what call points are made by bte's in your system?
any other clues on how to change bseg-zlspr wit an exit?
Posted: Thu Oct 11, 2007 1:15 am
Unfortunately I'm no where near a system nor OSS at the moment, however, have a search on OSS for FI SUBTITIONS ADDITIONAL FIELDS (or some such).
There is an OSS note which tells you how to add additional fields to those allowed in FI substition.
That might help.
If I manage to get n a system today, I'll try and remember to find it fr you.
Posted: Thu Oct 11, 2007 2:29 am
Have a look at OSS Note 20637. This describes how to add additional fields to substitutions and validations.
For people who do not have access to OSS:
OSS Note 20637 wrote:
You must enter the fields in Table GB01C which permits fields belonging to the Boolean class. To do so use view V_GB01C (transaction code SM30); the necessary codes will automatically be generated.
You can only include fields from already permitted tables. A table is permitted if, for example, the following entry exists in table GB01:
BOOLCLASS CLASSTYPE BCLTAB BCLFIELD BEXCLUDE
001 B COBL *
BCLFIELD has to have the entry * and BEXCLUDE has to be blank.
Tables which are not defined in the table GB01 can also be made unavailable for validations or substitutions using the view V_GB01C, since the structures and tables are transferred statically when the validation or substitution is called up.
You should also take into consideration that fields which have been excluded by SAP because of an entry in table GB01, cannot be maintained using the view V_GB01C (SAP definitions take precedence over customer definitions).
In Release 2.1, you must manually generate the codes. Call up Report RGUGBR00 and select the parameters 'Generate table files' and 'Generate substitution routines'. You can improve the system performance time by limiting the generation process to your application area and callup point.
There are other specific notes about adding coding block fields to the field substitution list but I cannot lay my hands on them directly.