incomplete document trasaction

[Former Member]

Hi,

Is there a transaction to view incomplete document log.

For eg. in contracts we can view an incomplete document log, but can i straightaway go to that transaction.

Regards,

Vijay

[Former Member · Accepted solution]

Hi Vijay

For displaying incomplete documents: Transaction - 'V.00'

For displaying incomplete contracts: Transaction - 'V.06'

for other kinds of incomplete documents, u can try table TSTCT, see entries for language (SPRSL)- english 'EN' (see all entries in table) and search for keyword 'incomplete' in 'TTEXT' column.

Cheers

Ashish

[Former Member · Accepted solution]

that is for displaying all incomplete documents. Already tried that out..What I was looking at was like given the document number it would take me to the incompletion log..Maybe it's not possible...There might not be a straight transaction for it..

Thanks,

Regards,

Vijay

[Former Member · Accepted solution]

Hi!

Results of small investigation - V.* transactions use simple CALL TRANSACTION to jump to document incompletion log.

Here it is adopted for your requirement working "copy-paste" source:

PARAMETERS:

p_vbeln type vbak-vbeln.

DATA: BEGIN OF bdcdata OCCURS 500.

INCLUDE STRUCTURE bdcdata.

DATA: END OF bdcdata.

DATA: ctu_params LIKE ctu_params.

DATA: BEGIN OF xvbak OCCURS 100.

INCLUDE STRUCTURE vbak.

DATA: END OF xvbak.

SELECT SINGLE *

INTO CORRESPONDING FIELDS OF xvbak

FROM vbak

WHERE vbeln = p_vbeln.

CLEAR bdcdata.

REFRESH bdcdata.

bdcdata-program = 'SAPMV45A'.

IF xvbak-vbtyp CO 'EF'.

bdcdata-dynpro = '0125'.

ELSE.

bdcdata-dynpro = '0102'.

ENDIF.

bdcdata-dynbegin = 'X'.

APPEND bdcdata.

*- Belegnummer -

---

*

CLEAR bdcdata.

*- Dynpro-Feldname setzen -

---

*

*- Dynpro-field name -

---

*

bdcdata-fnam = 'VBAK-VBELN'.

*- Feldinhalt setzen -

---

*

*- contents -

---

*

bdcdata-fval = xvbak-vbeln.

APPEND bdcdata.

*- Fcode UER2 fr Unvollstôndigkeitsprotokoll setzen -

---

*

CLEAR bdcdata.

*- Dynpro-Feldname setzen -

---

*

*- Dynpro-field name -

---

*

bdcdata-fnam = 'BDC_OKCODE'.

*- Feldinhalt setzen -

---

*

*- contents -

---

*

bdcdata-fval = 'UER2'.

APPEND bdcdata.

CLEAR bdcdata.

bdcdata-program = 'SAPMV45A'.

bdcdata-dynpro = '4001'.

bdcdata-dynbegin = 'X'.

APPEND bdcdata.

*- Fcode FEAZ fr Unvollstôndigkeitsprotokoll setzen -

---

*

CLEAR bdcdata.

*- Dynpro-Feldname setzen -

---

*

*- Dynpro-field name -

---

*

bdcdata-fnam = 'BDC_OKCODE'.

*- Feldinhalt setzen -

---

*

*- contents -

---

*

bdcdata-fval = 'FEAZ'.

APPEND bdcdata.

*- Unvollstôndigkeitsprotokoll -

---

*

CLEAR bdcdata.

bdcdata-program = 'SAPMSSY0'.

bdcdata-dynpro = '0120'.

bdcdata-dynbegin = 'X'.

APPEND bdcdata.

ctu_params-dismode = 'E'.

ctu_params-nobinpt = 'X'.

*--Aufruf der Ônderungstransaktion nach VBTYP--

-

---

CASE xvbak-vbtyp.

WHEN 'A'.

CALL TRANSACTION 'VA12' USING bdcdata

OPTIONS FROM ctu_params.

WHEN 'B'.

CALL TRANSACTION 'VA22' USING bdcdata

OPTIONS FROM ctu_params.

WHEN 'C'.

CALL TRANSACTION 'VA02' USING bdcdata

OPTIONS FROM ctu_params.

WHEN 'E'.

CALL TRANSACTION 'VA32' USING bdcdata

OPTIONS FROM ctu_params.

WHEN 'F'.

CALL TRANSACTION 'VA32' USING bdcdata

OPTIONS FROM ctu_params.

WHEN 'G'.

CALL TRANSACTION 'VA42' USING bdcdata

OPTIONS FROM ctu_params.

WHEN '0'.

CALL TRANSACTION 'VA42' USING bdcdata

OPTIONS FROM ctu_params.

WHEN OTHERS.

CALL TRANSACTION 'VA02' USING bdcdata

OPTIONS FROM ctu_params.

ENDCASE.

Regards,

Maxim.

[Former Member]

anyone...