bdc recording for F-02

[Former Member]

Hi Experts,

I am recoding a bdc for the transaction F-02. I am just filling in mandatory fields (Document Date, Type, Company Code, posting date, Currency, Posting Key and Account) in the first screen.

In the next screen am filling the Amount and Tax Code. I am also filling the Next line item with Posting key as 50.

My doubt arises here. When I click on Enter, am getting a pop up screen called CODING BLOCK. It is having some fields like Order, WBS element.

In the same way after i enter the credit amount in the third screen and press Enter, again am getting a CODING BLOCK screen with no fields in it.

I am not getting this CODING BLOCK pop up when i execute the Transaction F-02, but if i record the transaction, this scenario happens. Please explain me why this is happening?

Thanks in advance,

Mohamed Aslam

[Former Member]

Hi,

When you your recording using SHDB, please tick the attribute 'Not a batch input session'.

SAP has coded different behavior between online and batch input mode, as batch input mode requires simpler screen than normal screen.

Regards,

Lim...

[Former Member]

Thanks a lot,

if possible can you explain the following checkboxes also,

1) Default Size

2) Cont.after commit

3) not a batch input session

4) END: Not a Batch Input session

5) Simulate Background mode

Actually i found the description of these but am not able to find how they actually give the difference in a recording. For example in a similar way you explained "Not a batch input session".

In short I would like to know the impact of these check boxes in recording rather than what they are.

Experts waiting for reply

Thanks,

Aslam

[Former Member]

Hi Mohamed,

1. Default Size selection is used to check whether the screens of the called transaction are displayed in the standard screen size.

I would recommend you to always set this option to 'X' so that user screen resolution is used but the internal default screen size is used. This is especially true when the screen has table control

2. Cont.after commit selection is used to check whether the COMMIT WORK statement terminates batch input processing or not. If the value is 'X', then COMMIT WORK does not terminate processing.

3. Not a batch input session selection is used to set system field sy-binpt.

This is the value that SAP use to know whether this is batch input mode ('X') or on line mode (' ') and code the screen behavior accordingly.

4. END: Not a Batch Input session selection is used to set system field sy-binpt at the end of the batch input data in the called transaction.

So you have the batch input session (sy-bpint = 'X'), but at the end of the session you want it to behave as normal (like the option 3) again. This could be that you join 2 session in your program and 1 session is using batch input mode and the other one is not batch input mode.

5. Simulate Background mode  selection is used to set sy-batch.

And again this is the value that SAP use to know whether this is background mode ('X') or on line mode (' ') and code the screen behavior accordingly.

Regards,

Lim...

[Former Member]

hi,

In the OK_CODE in BDC recording change the value of \00 to =ENTR or =ENTE one of this should suppress the pop-up as soon as its filled with appropriate Cost center value..

else you have another way to handle that pop up but its a tedious..instead of recording through SHDB you can carry out the a manual recording such as

in a report program use CALL TRANSACTION 'F-02'. while navigating through every screen check for F1 for technical names of the fields in that screen and for every navigation from one screen to following one check for SY-UCOMM VALUE this way you get the pop up to and also its technical name.

check this link too...

[Transaction F-02|;

Regards

Sharath

[Sougata]

Hi Aslam,

Its nothing but the Account Assignment detail area the info which the system may or may not require before it can post a document as per the FI system is configured.

When you do normal (online) F-02, on the line-item screen, there's a pushbutton named "=>More" on the right hand side (middle of the screen). On the line-item screen if the system needs more (i.e. Account Assignment) info before it can post a document for e.g. Profit Centre, CO object etc, the system automatically pops this up with a message to force the user to input one or the other required assignments. However, in the online mode, if no additional info is required by the system before it can post the document, it does not pop-up anything, which makes sense - but the user, at that point, if wants to save additional info can click on this button and input the Profit Centre number for example before posting the document.

Unfortunately the BDC technology is old and not so smart As the BDC technology relies and runs through every single dynpro (or "screen-by-screen") of a transaction, while the application is in the BDC mode, it will still pop-up the Account Assignment details box (Coding Block pop-up box) because that is also a separate dynpro which must be called by the system! Now do you know why I called it a "not-so-smart" technology?:-) But at the same time its logical because the application/user is in batch mode and no one can push the "=>More" button if he wants to save the additional info! So, it gives you an option by poping up that box even if acct. assignment info is not mandatory to save the current document.

In your program, all you have to do is first ascertain if this is a required info or not to be able to post this document - if it is then input the required fields and then press enter - if it is not, just press the enter (green tick) without filling anything in which will prompt the F-02 application to continue to post the document.

Hope this throws some light on the subject and I personally think you should get away from this BDC stuff and start using Business Objects (BAPIs) unless there is a solid reason as why you can't achieve the results with a BAPI.

Cheers,

Sougata.