Problema Bach Imput MIRO

[hanzzou]

Hola, estoy teniendo un problema al realizar un Batch Input en la transacción MIRO.
- Si ejecuto el reporte desde la SE38 funciona perfecto! incluso tira los mensajes de error que puse en el codigo.
- Si ejecuto desde la transaccion creada para el reporte, no me ejecuta el reporte, sino que sale y vuelve al SAP Easy Access y tampoco me muestra mensajes de error que deberia mostrar.

Tienen idea que puede estar pasando?
Gracias!

Saludos,

[mystic_soul]

Para mi, debe ser que la transaccion está mal creada.. fijate si el reporte está seleccionada para que sea de reporte (valga la redundancia) y que no sea de screens...
Espero que se haya entendido..

Salutes!!

[guillermogpaz]

Problema Bach Imput MIRO

Hola como estas, yo hace tiempo quise hacer lo mismo. Te paso la siguiente nota sap. Espero que te sirva.

Note 381593 - MIRO/MIR7/MIRA: Batch Input is not possible
Note Language: English Version: 9 Validity: Valid from 02.11.2005
Summary
Symptom
Batch input processing is not possible for the following transactions in
invoice verification:
o Add incoming invoice (MIRO)
o Park incoming invoice (MIR7)
o Add incoming invoice for the verification in the background (MIRA)

Various errors can occur.
More Terms
BAPI, BAPI_INCOMINGINVOICE_CREATE, BAPI_INCOMINGINVOICE_SAVE,
BAPI_INCOMINGINVOICE_PARK, BAPI_INCOMINGINVOICE_CREATE,
BAPI_INCOMINGINVOICE_GETDETAIL, BAPI_INCOMINGINVOICE_GETLIST,
BAPI_INCOMINGINVOICE_RELEASE, BAPI_INCOMINGINVOICE_CANCEL,
CTNL_ERROR, CALL TRANSACTION, MIR4

Cause and Prerequisites
The new Enjoy transactions of the logistics invoice verification have not
been planned for the use with Batch Input or 'CALL TRANSACTION'.
The reason for this is that the Batch Input is based on screen technology,
but the Enjoy transactions are more and more based on control technology.
Batch Input and controls are not compatible.

Solution
Release 4.6A - 4.6B
o Use the following BAPIs:
Object name: IncomingInvoice
Object type: BUS2081
Method: CreateFromData (add incoming invoice)
CancelSingle (cancel incoming invoice)
ReleaseSingle (release incoming invoice)
GetList (list incoming invoice)
GetDetail (display incoming invoice)
o The conventional transactions of invoice verification (MR01, MR1H,
MR41, MR1B) and the logistics invoice verification (MR1M) are
supported in the Releases 4.6A up to and including Release 4.6B.

These transactions make Batch Input processing possible.
As of Release 4.6C
o Use the following BAPIs:
Object name: IncomingInvoice
Object type: BUS2081
06.09.2007 Page 2 of 3
Note 381593 - MIRO/MIR7/MIRA: Batch Input is not possible
Method: CreateFromData (add incoming invoice)
CancelSingle (cancel incoming invoice)
ReleaseSingle (release incoming invoice)
GetList (list incoming invoice)
GetDetail (display incoming invoice)
ParkFromData (park incoming invoice)
SaveFromData (mark incoming invoice for
background verification)
o The conventional transactions of the invoice verification (MR01,
MRHG, MRHR, MR41 up to MR44, MR1G, MR1B) are no longer maintained
as of Release 4.6C.
o Transaction MR1M of the logistics invoice verification will be
deleted for Release 4.6C since it will be replaced completely by
the MIRO in terms of functionality.
The following function modules are assigned to the methods:
CreateFromData: BAPI_INCOMINGINVOICE_CREATE
CancelSingle: BAPI_INCOMINGINVOICE_CANCEL
ReleaseSingle: BAPI_INCOMINGINVOICE_RELEASE
GetList: BAPI_INCOMINGINVOICE_GETLIST
GetDetail: BAPI_INCOMINGINVOICE_GETDETAIL
ParkFromData: BAPI_INCOMINGINVOICE_PARK
SaveFromData: BAPI_INCOMINGINVOICE_SAVE.

[Marco]

Exacto... La incopatibilidad es.
Ahora mejor utiliza BAPIS, son mas seguras, flexibles, te devuelve siempre una tabla de ejecución y corren los mismos procesos de negocios de SAP.

Sld,

[hanzzou]

gracias!!!!

El problema era como estaba creada la transaccion, yo lo recibi para controlar y solo me fijaba en problemas de codigo.

muchas gracias.