general

[Former Member]

what is the exact use of rfbibl00 program if u can plz explain with taking simple example.

[Former Member]

Hello,

Short text

    Batch Input Documents

Use

    The RFBIBL00 program is used for entering accounting documents and for
    clearing open items. This is done by importing and processing a UNIX
    file with the structure described below.

    The program is primarily intended for generating batch input sessions.
    Documents can, however, also be generated immediately using "call
    transaction" or "direct input" by means of the "Data transfer type"
    parameter. Both of these procedures lead to improvements in system
    performance when transferring large quantities of data (more than 10,000
    transactions).

    The difference between a call transaction and batch input is that the
    documents are posted immediately by calling the corresponding
    transactions. The same screens are processed as for batch input.
The documents are also posted immediately with direct input. The
improvement in system performance compared with a call transaction is
achieved because no screens are processed and the documents are
therefore posted directly by calling function modules. Direct input is
only available for some of the posting options. No FB05 postings
(posting with clearing), FBS1 postings (accrual/deferral documents),
FBV1 postings (park document), nor postings with special G/L
transactions can be generated.

Restart mechanism

Since the documents are posted immediately into the SAP System with
"call transaction" or "direct input", you must take precautions to allow
a program restart after a program termination. This restart (which is
referred to here as the restart mechanism), is used to prevent duplicate
posting of documents during a new program start.

If you select call transaction or direct input, you should definitely
use the restart mechanism. To do this, carry out the following steps:

o   First of all create a variant for the RFBIBL00 program.
     Proceed

 o   Define a job which can be restarted.
     Proceed.

 o   Start the job which can be restarted.
     Proceed.

 Requirements for the restart mechanism:

 o   The input file may not contain any formal errors. This can be
     established using the "Check file" parameter. The restart procedure
     cannot be used if there is a termination due to a formal error. You
     must then find out yourself which documents were posted up until the
     termination and then reduce the file correspondingly.
     If a file which is to be processed using direct input contains FB05
     transactions, then a termination occurs without a restart option.

 o   The program may only be imported in the way described above.

 o   Transactions with errors are collected in a batch input session. The
     session name of the first BGR00 record is always used.
  Direct input or call transaction can also be used without the restart
  mechanism for test purposes. In this case, however, the input file may
  no longer contain more than 20 transactions. A restart after a program
  termination is, however, then not possible.

te

  Structures:

  o   Information which affects the entire batch input session is defined
      in the session prefix.

  o   Information which applies to an entire document is defined in the
      header record.

  o   The document fields for which batch input is to be possible are
      defined in separate Data Dictionary structures.

  Each structure is identified by record type and possibly by table name.

  The structures, in detail, are:

  o   BGR00 record type 0 session prefix

  o   BBKPF record type 1 header data

  o   BBSEG record type 2 document segment data (including one-time data,
      COBL data)

  o   BBTAX record type 2 document taxes (see paragraph on "New entry
      methods
      for tax amounts")

  o   BWITH record type 2 document withholding tax data (extended
      withholding
                          tax functions; FB01 and FBV1 only)

  o   BSELK record type 2 selection header data (FB05 only)

  o   BSELP record type 2 selection items (FB05 only)

  For each field which is transferred to the batch input structure, you^
must decide whether the value of the field is initial (for example, the
field should be reset to zero) or whether no batch input at all is
necessary for this field.

This means that a special character must be specified which has the
function: "No batch input for this field".

This special character is the character "/" by default.

If you do not wish to use the special character "/", you can specify
another special character in the session prefix in field BGR00-NODATA,
which will carry out this function.

Before filling the batch input structure, each structure field (except
the session prefix BGR00) must be "prepared" at the beginning of the
field with this special character.

The structure fields refer to data elements of fields from the original
tables. However, numeric and packed fields are an exception. These need
separate data elements of category CHAR for batch input, since packed
fields cannot be "initialized" with a special character.

That means that amounts can be transferred with decimal points to the
interface.


Record end indicator:

If a batch input structure is extended later, the new end of the
structure is indicated by a special field (SENDE). If you are already
working with the new, extended structure, then enter the special
character NODATA in this field when "initializing" the structure. You
can then see when importing the structure whether the data is based on
the old or the new structure.


Special fields in the session prefix:

In the session prefix, the batch input session name must be given
(BGR00-GROUP). Sending a further session prefix causes the closing of
the current session and the opening of a further session.

In the session prefix, you can transfer the special character
BGR00-NODATA.

REgards,

Vasanth

[Former Member]

Hi,

The RFBIBL00 program is used for entering accounting documents and for

clearing open items. This is done by importing and processing a UNIX

file with the structure described below.

The program is primarily intended for generating batch input sessions.

Documents can, however, also be generated immediately using "call

transaction" or "direct input" by means of the "Data transfer type"

parameter. Both of these procedures lead to improvements in system

performance when transferring large quantities of data (more than 10,000

transactions).

For documentation goto se38 give the program name and follow this path i.e, GOTO-> DOCUMENTATION ..

Regards

[Former Member]

Hi

The RFBIBL00 program is used for entering accounting documents and for clearing open items. This is done by importing and processing a UNIX file with the structure described below.

The program is primarily intended for generating batch input sessions. Documents can, however, also be generated immediately using "call transaction" or "direct input" by means of the "Data transfer type" parameter. Both of these procedures lead to improvements in system performance when transferring large quantities of data (more than 10,000 transactions).

The difference between a call transaction and batch input is that the documents are posted immediately by calling the corresponding transactions. The same screens are processed as for batch input.

The documents are also posted immediately with direct input. The improvement in system performance compared with a call transaction is achieved because no screens are processed and the documents are therefore posted directly by calling function modules. Direct input is only available for some of the posting options. No FB05 postings (posting with clearing), FBS1 postings (accrual/deferral documents), FBV1 postings (park document), nor postings with special G/L transactions can be generated.

Restart mechanism

Since the documents are posted immediately into the SAP System with "call transaction" or "direct input", you must take precautions to allow a program restart after a program termination. This restart (which is referred to here as the restart mechanism), is used to prevent duplicate posting of documents during a new program start.

If you select call transaction or direct input, you should definitely use the restart mechanism. To do this, carry out the following steps:

First of all create a variant for the RFBIBL00 program.

Proceed

Define a job which can be restarted.

Proceed.

Start the job which can be restarted.

Proceed.

Requirements for the restart mechanism:

The input file may not contain any formal errors. This can be established using the "Check file" parameter. The restart procedure cannot be used if there is a termination due to a formal error. You must then find out yourself which documents were posted up until the termination and then reduce the file correspondingly.

If a file which is to be processed using direct input contains FB05 transactions, then a termination occurs without a restart option.

The program may only be imported in the way described above.

Transactions with errors are collected in a batch input session. The session name of the first BGR00 record is always used.

Direct input or call transaction can also be used without the restart mechanism for test purposes. In this case, however, the input file may no longer contain more than 20 transactions. A restart after a program termination is, however, then not possible.

Reward points if useful

Regards

Anji

[Former Member]

Hai,

The RFBIBL00 program is used for entering accounting documents and for clearing open items. This is done by importing and processing a UNIX file with the structure described below.

The program is primarily intended for generating batch input sessions. Documents can, however, also be generated immediately using "call transaction" or "direct input" by means of the "Data transfer type" parameter. Both of these procedures lead to improvements in system performance when transferring large quantities of data (more than 10,000 transactions).

The difference between a call transaction and batch input is that the documents are posted immediately by calling the corresponding transactions. The same screens are processed as for batch input.

The documents are also posted immediately with direct input. The improvement in system performance compared with a call transaction is achieved because no screens are processed and the documents are therefore posted directly by calling function modules. Direct input is only available for some of the posting options. No FB05 postings (posting with clearing), FBS1 postings (accrual/deferral documents), FBV1 postings (park document), nor postings with special G/L transactions can be generated.

Regards,

Padmam.

[Former Member]

refer this link