3 Answers

• 00

  

  MrBojangles 10/20/23, 12:32 PM

  Hello Schnipsi,
  what kind of data do you want to store in this additional field (data type, manually entered or derived). Perhaps a standard field would be suitable to hold this information. Otherwise, I would actually extend the coding block, because this ensures a continuous/seamless usability and update of the additional field.
  Continue to have fun with SAP...
  Cheers
  MrB.
  Blog

  report
• 00

  

  Schnipsi (Author)10/20/23, 12:32 PM

  Hello,
  thanks for the first feedback!
  In principle CHAR(10), entered manually, but based on a predefined value list (so that no letter twists or the like come out). I.e. not derivable / verifiable based on other information in the document.
  Extension COBL (BSEG) is, as I said, too much in relation to the scope of the documents for which this additional information is needed - there would also be new field status groups necessary to display the new fields only for those company codes for which they are actually needed, etc. ==> we'd better leave that for this very narrow application area :-) Our BSEG currently has >800 million entries, in fiscal year 2019 alone more than 80 million. I expect a maximum 4-digit number of booking lines that should contain the new information...
  The way via a Z-table seems easier to me - incl. maintenance of this in the follow-up to the actual FI posting. This would then only have to be "marked" so as not to forget the additional information - but we'll get there!

  report
• 00

  

  Schnipsi (Author)10/20/23, 12:32 PM

  Hello!
  Have the solution now almost ready, works wonderfully ==> when saving the document I call via the BTEs 1030 (Post document), 1110 (Change document), 1050 (Post document via e.g. MIRO) the popup (except for background processing), the user can make his entries and I save the values in a Z-table.
  Later mass maintenance of this Z-table is also already solved.
  I still have one flaw - with e.g. FB02, the BTE 1110 is *not* run through, if nothing is changed on the document itself. As a workaround, I currently have only (1) the downstream mass maintenance of the Z-table or (2) some detail on the document (header text, segment text, ...) to change, so that the BTE 1110 is run through.
  Do you know of any way that this BTE (or from me another one that has access to the document header) is run through, even if *no* change is made to the document itself?
  Thanks & best regards,
  Schnipsi

  report