Check out the mass documents(BAPI_DOC_MASS_CHECKOUTVIEW2) execution details

[former_member188831]

Dear Friends,

We have requirement to download all the documents(Attachments for each document nuber in CV02) along with their childs.

for that we come across one function module i.e BAPI_DOC_MASS_CHECKOUTVIEW2.

But this FM is not downloading the attachmetns to our local system.

Please let me know how it works and from where it is picking the documents.

Even we need the relation shipt these documetn for which Specification(document).

Thanks,

Mahesh.Gattu

[christoph_hopf]

Hi Mahesh,

unfortunately I cannot offer you a detailed sample which could be used for this behavior. Because this depends on several system related variables. From our internal test system I can only provide you the following sample data which might be useful for your. Generally the tables DOCUMENTSTRUCTURE and DOCUMENTFILE needs to be filled like:

DOCUMENTSTRUCTURE
X DRW TEST_CHECKOUT_1           000 00 
X DRW TEST_CHECKOUT             000 00

DOCUMENTFILE

1st original:                                                     
DELETEVALUE                    X
DOCUMENTTYPE                   DRW
DOCUMENTNUMBER                 TEST_CHECKOUT_1
DOCUMENTPART                   000
DOCUMENTVERSION                00
ORIGINALTYPE                   1
SOURCEDATACARRIER
STORAGECATEGORY                DMS_C1_ST
WSAPPLICATION                  JPG
DOCPATH
DOCFILE                        C:\DOCUMENTS AND SETTINGS\I045553\SAP
STATUSINTERN
STATUSEXTERN
STATUSLOG
APPLICATION_ID                 4B18F253E70B2282E10000000A421377
FILE_ID                        4B18F255E70B2282E10000000A421377

2nd original
DELETEVALUE                    X
DOCUMENTTYPE                   DRW
DOCUMENTNUMBER                 TEST_CHECKOUT_1
DOCUMENTPART                   000
DOCUMENTVERSION                00
ORIGINALTYPE                   2
SOURCEDATACARRIER
STORAGECATEGORY                DMS_C1_ST
WSAPPLICATION                  JPG
DOCPATH
DOCFILE                        C:\DOCUMENTS AND SETTINGS\I045553\SAP
STATUSINTERN
STATUSEXTERN
STATUSLOG
APPLICATION_ID                 4B18F253E70B2282E10000000A421377
FILE_ID                        4B18F258E70B2282E10000000A421377

Further please made sure that SAP note 1445865 is also implemented in your system to avoid the described issue.

Best regards,

Christoph

[former_member188831]

Thanks Christoph and Lijo,

I am trying to execute the BAPI with the below parameters.

Header:

ORIGIGNAL PATH: V:\PIMS (LOcal paht from my system)

HOSTNAME:DEFAUTL

PF_HTTP_DEST:LOCL

PF_FTP_DEST:

Pleae let me know the above header params are correct ?

ORIGINALPATH: V:\PIMS\ (It is created by me on my local machine).

Then Tables

Document Structure i entered as below

😧 X

Doc:P02

Document Number:2000001520

DOc:000

DO:00

For document file

😧 X

Doc:P02

Document Number:2000001520

DOc:000

DO:00

ORIGI:1

Source Data:

Storage Cat:SMA_C1_ST

Docpath: V:\PIMS| (System local path)

I just doubted here DOCPATH: V:\PIMS\ again i mentioned my local directory on my desktop.

But is this is correct.

after execution i got message like:

Connection to V:\PIMS\_IMGATTU03.txt failed.

Please let me know how it will get down loads the files(attachments) to my local machine.

Thanks,

Mahesh.Gattu

[former_member233637]

Hi Christoph,

I use the BAPI   BAPI_DOC_MASS_CHECKOUTVIEW2  but get runtime error . 

'CX_SY_DYN_CALL_PARAM_MISSING', was

     not caught in

    procedure "CV120_KPRO_MASS_CHECKOUT" "(FUNCTION)", nor was it propagated by a

     RAISING clause.

    Since the caller of the procedure could not have anticipated that the

    exception would occur, the current program is terminated.

    The reason for the exception is:

    When calling the function module "SDOK_MASS_PHIOS_GET_COPY", one of the

     parameters

    needed according to the interface description was not specified.

    This parameter was "OBJECT_FILE_INFORMATIONS".

I found SAP-Note 1098739 regarding the missing parameter.

But this Note is for Release  500 only     

SAP_APPL

500

500

500

But we have Release SAPKH60605 and should already have the correction in our release.

 

Are there other SAP-Notes which solves this problem?

Regards Josef.

[Former Member]

Hi Mahesh,

I have seen in SDn forum about another BAPI - BAPI_DOCUMENT_CHECKOUTVIEWX

Have a try and let us know whether you were successfull.

Regards,

Lijo Joseph