Draft DocEntry is affected by Print Previews

[mbanggo]

Hi Everyone,

Good day!

We have a weird scenario with regards to SAP B1 Draft Documents. We have saved a Draft Goods Issue with DocEntry 1095, for example. When we did a print preview twice, the layout shows a docentry of 1096 for the first preview then 1097 for the 2nd preview. The docentry increases everytime we preview the layout. However, in the database only 1095 is in the ODRF Table. When we saved another Goods Issue draft, the draft has a docentry of 1098. The draft list only has 1095 and 1098 as drafts.

Is this normal? What's the reason for this? Our client needs a draft number to be printed in the Draft Goods Issue but because of the increasing docentry during reprints, they can no longer trace the printed document against the docentries in the ODRF table.

Any idea or resolution will be highly appreciated.

Thank you very much and God bless.

Sincerely,

Melvin

[nikunjmehta2290]

Hi MelVin,

DocEntry has been increased due to anther document has been added into system even in draft mode or without draft mode. You can use the internal number / document number in print purpose to close your requirements.

Regards,

Nikunj Mehta

[mbanggo]

Hi Nekunj Mehta,

The internal number / document number is the docentry in ODRF, right? We are already using this in our print layout and the printed number does not coincide with the one in the database. This is our problem which is weird since we are already using the docentry. Or is there another field that we can use?

Sincerely,

Melvin

[nikunjmehta2290]

Hi Melvi,

Internal number and document number is not same in ODRF. If someone is delete the draft document and create the another draft document (here same document) then sap is taking next number as a internal number instead of previous number. So, In each case user getting new internal number.

Suggest to you use the document number in print purpose or create one UDF and mention the number as per your requ and use it in layout.

Kind regards,

Nikunj

[tungnguyenthanh]

We have the same issue.

Have you found the solution?

[mbanggo]

Unfortunately, no.