BAPI_DOCUMENT_CREATE2 fails in Background

Question

Hi everyone,
I wrote an ABAP-report calling BAPI 'BAPI_DOCUMENT_CREATE2'.
This ABAP has to create a document and upload files per FTP into DMS (Checkin)
Works Online fine (cause the BAPI avoids FTP as a GUI is online available)  but miserably fails in background:
Message: RFC callback calls are not allowed in the ABAP...
This message comes from a failed call of the FM 'SYSTEM_START_REG_SERVER'
in the FM  'CV120_FTP_START_REG_SERVER' as described in an old thread (Error in Check in of Originals by BAPI In background)
Sample of the BAPI-call:
  CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
    EXPORTING
      documentdata         = documentdata
      pf_ftp_dest          = 'SAPFTPA'
    IMPORTING
      documenttype         = documenttype
      documentnumber       = documentnumber
      documentpart         = documentpart
      documentversion      = documentversion
      return               = return
    TABLES
      documentdescriptions = documentdescriptions
      objectlinks          = objectlinks
*      documentstructure    = documentstructure.
*      documentfiles        = documentfiles
*      documentstructure    = documentstructure.
      documentfiles        = documentfiles.
I tried a lot, even in 2 steps (first create the doc per BAPI, second checkin per call of CVAPI_DOC_CHECKIN)
but in everycase, i always get the same problem...
Any help will greatly be appreciated : i daily and manually (ok, even if 1 report launch per day is sufficent) have to upload aprox.
2000 PDFs ...
Thanks in advance for answering...
Edited by: Guillaume Delorme on May 5, 2010 11:08 AM

Answer 1

Hi everyone,
Due to holidays, i gotta  post under another account...
There was a logical mistake in my problem:
-> i thought i had to do the physical checkin of the files while or after the BAPI_DOCUMENT_CREATE2-call.
In my case, the content-server is reachable from the app-server as it's been defined in the AL11.
The content-server is directly defined in table TDWD with complete directorypath as a vault-server (NO DVA-VAULT).
The SAP-FBs do actually handle two cases for file-checkin that can suit my concern::
-> DVA-Vault?->FTP-Connect for filetransfer
-> No DVA-Vault? ->Local GUI-Upload  for filetransfer
For background-processing fails always the GUI-Upload -> normal
I don't use any DVA-Vault -> i must do something else.
Solution: Ridiculously easy...
*-> FIRST :Physical Checkin over a stupid TRANSFER DATASET for the file.
*If OK:
*->SECOND: Call of  BAPI_DOCUMENT_CREATE2 with reference to the transferred File
*      ->Structure BAPI_DOC_DRAW2:
*          -> Short Dataname in BAPI_DOC_DRAW2-docfile1
*          -> Datacarrier in BAPI_DOC_DRAW2-datacarrier1 (actually the key for the VAULT-server)
*          -> App.type in BAPI_DOC_DRAW2-wsapplication1.
*          -> Description, Documentype, username, laboratory are must-fields with my customizing too.
*       ->Internal Table BAPI_DOC_FILES2:
*          -> Short Dataname in BAPI_DOC_FILES2-docfile
*          -> Datacarrier in  BAPI_DOC_FILES2-storagecategory (actually the key for the VAULT-server)
*          -> App.type in BAPI_DOC_FILES2-wsapplication.
*          -> no other fields required for this table
*       ->(...)
*endif.
Now it runs fine every 5 minutes and i handle about 3000 documents a day...
I give points to Phillip van den Heever who reminded me the AL11-Setting and i mark this topic solved as soon as i can...
Thanks to everyone and greets,
Guillaume Delorme