Document Types and Number Range Objects in New GL

If you use a ledger group to make account assignments for postings, it is only possible to verify that document numbers are assigned contiguously at the ledger ... Skiptocontent Skiptobreadcrumbs Skiptoheadermenu Skiptoactionmenu Skiptoquicksearch ERPFinancialsPagesBrowsepagesConfigureSpacetools Attachments(2) PageHistory PageInformation Resolvedcomments ViewinHierarchy ViewSource ExporttoPDF ExporttoWord Pages … ERPFinancials FinancialAccounting GeneralLedger DocumentSplitting GeneralDocumentation-DocumentSplitting DocumentSplittingSettings Skiptoendofbanner Jiralinks Gotostartofbanner DocumentTypesandNumberRangeObjectsinNewGL Skiptoendofmetadata CreatedbyCoraPhelan,lastmodifiedonDec18,2019 Gotostartofmetadata DocumentTypesandNumberRangeObjectsinNewGLPurposeThepurposeofthisdocumentistooutlinethecustomizingfordocumenttypesandnumberrangeobjectsinNewGL.OverviewThisdocumentgoesthroughthecustomizingstepsfordocumenttypesandnumberrangeobjectsinnewGL.DocumentTypesandNumberRangeObjectsinNewGL Themenupathforcustomizingdocumenttypesandnumberrangeobjectsinnew GLisasfollowsDocumenttypesinEntryView ThefieldforthedocumentnumberisBELNRThedocumenttypesintheentryviewaredefinedintransactionOBA7(TableT003).ThemenupathviaIMGforsameisFinancialAccounting(New)->FinancialAccountingGlobalSettings(New) ->Document->DocumentTypes->DefineDocumentTypesforEntryViewThenumberrangeisassignedtothedocumenttype.ThenumberrangeobjectisRF_BELEG*RecommendationInOBA7documenttypesshouldbeassignedtothenumberranges01-90.   TheIMGactivitydocumentationonDefineDocumenttypesforEntryView statesthefollowing:DefineDocumentTypesforEntryViewUseInthisactivity,youdefineyourdocumenttypes.Documenttypesareusedtodifferentiatethebusinesstransactionsandtomanagehowdocumentarestored.ThisdocumentationdescribesthespecialprocedureforsettingupdocumenttypesforNewGeneralLedgerAccounting.Forgeneralinformationaboutdefiningdocumenttypes,seeDefineDocumentTypes.ActivitiesIfyouonlyworkwithoneledger(theleadingledger),proceedasfollows:Inthisactivity,defineforallpostingsthedocumenttypesforthedocumentsintheentryview.Alsoassignanumberrangetothedocumenttypes.Forexample:DocumentTypeSA,G/LAccountDocument,NumberRange01DocumentTypeSB,G/LAccountPosting,NumberRange12Ifyouworkwithaleadingledgerandwithnon-leadingledgers,proceedasfollows: Sincethemajorityofpostingshasthesameeffectinallledgers,defineinthisIMGactivitythedocumenttypesfortheentryviewforpostingsthataffectallledgers.Alsoassignanumberrangetothedocumenttypes.Example:DocumentTypeSA,G/LAccountDocument,NumberRange01DocumentTypeSB,G/LAccountPosting,NumberRange12Inthecaseofpostingsthatdonothavethesameeffectonallledger,proceedasfollows:Postingsonlyfortheleadingledger:Defineaseparatedocumenttypeforthesepostings.Assignauniquenumberrangetothisdocumenttype.Example:DocumentTypeSX,ClosingPostings,NumberRange90Postingsfornon-leadingledgers:YoumakethesesettingsunderDefineDocumentTypesforEntryViewinaLedger.NoteBysegregatingtheledger-relatedpostings(here,theleadingledger)inaseparatenumberrange,youensurethecontiguousassignmentofdocumentnumbersattheledgerlevelforeachnumberrange.DocumentTypesforEntryViewinaLedgerThefieldforthedocumentnumberisBELNRForledgerspecificpostingsdocumenttypesfortheentryviewofanon-leadingledger.The customizingview isV_FAGL_BELNR_LD ThemenupathviaIMGforsameisFinancialAccounting(New)->FinancialAccountingGlobalSettings(New)->Ledgers->Document->DocumentTypes->DefineDocumentTypesforEntryViewinaLedgerThenumberrangeisassignedtothecombinationofLedgerandDocumenttype(RLDNR+BLART).ThenumberrangeobjectisRF_BELEG*Recommendation:IntheviewV_FAGL_BELNR_LDdocumenttypesshouldbeassignedtothenumberranges91-95.TheIMGactivitydocumentationonDefineDocumenttypesforEntryViewinaLedgerstatesthefollowing:DefineDocumentTypesforEntryViewinaLedgerUseHere,youmakethesettingsspecifyingthedocumenttypeforpostingstonon-leadingledgers.UnderDefineDocumentTypesforEntryView,youmakethedocumenttypesettingsforpostingsintheentryviewthateffectallledgersandforpostingstotheleadingledger.RequirementsYouworkwithaleadingledgerandwithnon-leadingledgers. ActivitiesTodefinedocumenttypesforpostingstonon-leadingledgers,proceedasfollows:Setupaseparatedocumenttypeforthesepostings.Assignauniquenumberrangetothisdocumenttypeforeachledger.Example:DocumentTypeSX,ClosingPostings,LedgerL2,NumberRange91DocumentTypeSX,ClosingPostings,LedgerL3,NumberRange92NoteBysegregatingtheledger-relatedpostings(here,forthenon-leadingledgers)inaseparatenumberrange,youensurethecontiguousassignmentofdocumentnumbersattheledgerlevelforeachnumberrange.Withinaledgergroup,therepresentativeledgerdeterminesthedocumenttypesandnumberrangesapplied.Forthisreason,youcannotperformthisIMGactivityforaledgergroup.Ifyouusealedgergrouptomakeaccountassignmentsforpostings,itisonlypossibletoverifythatdocumentnumbersareassignedcontiguouslyattheledgerlevelfortherepresentativeledger.   DefineDocumentTypesforGeneralLedgerViewThefieldisDOCNR(tableFAGLFLEXA,oranothercustomerownNew-GLlineitemtable) Thecustomizingviewis V_FAGL_DOCNR_LDThemenupathviaIMGforsameisFinancialAccounting(New)->FinancialAccountingGlobalSettings(New)->Ledgers->Document->DocumentTypes->DefineDocumenttypesforGeneralLedgerView(NotethiscustomizingforDefineDocumentTypesforGeneralLedgerViewisonlyrelevantforreleasespriortosFINandS/4HANA)Thisonlyhastobemaintained,ifthenon-leadingledgerscontaindifferentfiscalyearvariantsastheoneassignedtotheleadingledger.ThenumberrangeobjectisFAGL_DOCNRTheassignmentofnumberrangestonumberrangeRF_BELEGandFAGL_DOCNRobjectshavetobedisjunctive.* TheIMGactivity DocumentationonDefineDocumentTypesforGeneralLedgerView statesthefollowing:DefineDocumentTypesforGeneralLedgerViewUseInthisIMGactivity,youdefinefornon-leadingledgersthedocumenttypesforthedocumentsintheGeneralLedgerview.Atthesametime,youassignforeachdocumenttypeanumberrangetobeappliedintheassignmentofdocumentnumbers:Youdonotneedtomakethesesettingsforyourleadingledgerbecause,inthecaseofthisledger,thedocumentnumberintheentryviewalwayscorrespondstothedocumentnumberinthegeneralledgerview.Youonlyhavetomakethesesettingsforanynon-leadingledgersthathaveafiscalyearvariantthatdiffersinatleastonecompanycodefromthefiscalyearvariantoftheleadingledgerinthiscompanycode.Inthiscase,thedocumentnumberintheentryviewdoesnotcorrespondtothedocumentnumberinthegeneralledgerviewandyouhavetodefineaseparatedocumenttypewithdocumentnumberassignmentforthegeneralledgerview.Forallnon-leadingledgersthat,inthecompanycodetowhichthepostingsaremade,haveafiscalyearvariantcorrespondingtothefiscalyearvariantoftheleadingledgerinthiscompanycode,thedocumentnumberintheentryviewalwayscorrespondstothedocumentnumberinthegeneralledgerview.NoteTheneedtodefineadocumenttypefordocumentsinthegeneralledgerviewdependsonlyonwhetherthefiscalyearvariantofthenon-leadingledgerinthecompanycode(towhichthepostingsaremade)differsfromthefiscalyearvariantoftheleadingledgerinthiscompanycode.Ontheotherhand,documenttypedefinitionindependentofwhichthetypeofledgergrouptowhichpostingsaremade,thatis,regardlessofWhetherpostingsaremadewithoutaledgergroupWhetherpostingsaremadetoaledgergroupwithaleadingledgerastherepresentativeledgerWhetherpostingsaremadetoaledgergroupwithanon-leadingledgerastherepresentativeledger NumberRangesNumberRangesinEntryViewThecustomizingforthe numberrangesforDocumentsin EntryViewis: SPRO->FinancialAccounting(New)->FinancialAccountingGlobalSettings(New)->Document->NumberRanges->DocumentsinEntryView->DefineDocumentNumberRangesforEntryView(TransactionFBN1)NumberRangesforDocumentsinGeneralLedgerViewThecustomizingforthe numberrangesforDocumentsinGeneralLedgerView is: SPRO->FinancialAccounting(New)->FinancialAccountingGlobalSettings(New)->Document->NumberRanges->DocumentsinGeneralLedgerView->DefineDocumentNumberRangesforGeneralLedgerView (TransactionFAGL_DOCNR)((Notethiscustomizingfor NumberRangesforDocumentsinGeneralLedgerViewisonlyrelevantforreleasespriortosFINandS/4HANA ))................................................................................................................................................................................................................................................................................................. Fornon-leadingledgerswithafiscalyearvariantequaltothefiscalyearvariantfromtheleadingledger0L,thedocumentnumberfromtheentryviewiscopiedtothenon-leadingledger.ThisdocumentnumberisderivedfromnumberrangeRF_BELEG.HoweverFornon-leadingledgerswithafiscalyearvariantdifferentfromthefiscalyearvariantfromtheleadingledger0L,aseparateledger-specificdocumentnumberisderivedfromnumberrangeFAGL_DOCNR. Foreachoftheseledgersaseparatedocumentnumberisderivedeveniftwoofthemhavethesamefiscalyearvariant.................................................................................................................................................................................................................................................................................................... *Thenumberrangesdonothavetofollowtherecommendationsasmentionedabove.Butitis very importantthatthenumberrangesusedininOBA7arenotusedinV_FAGL_BELNR_LD/V_FAGL_DOCNR_LD.................................................................................................................................................................................................................................................................................................... IncasenumberrangesforexampleFAGL_DOCNRandRF_BELEGarenotdefineddistinctivelythere wouldbeshortdumpsexpectedforexampleCHECK_DUPRECS_IN_TAB asthesystemcouldtrytoupdateFAGLDOCNRoncewithadocumentnumberofnumberrangeobjectFAGL_DOCNRandonceagainwithanumberrangederivedofnumberrangeobjectRF_BELEG. DocumentTypesandNumberswithSimpleFinance Themenupathforcustomizingdocumenttypesandnumberrangeobjectsinnew GLisasfollowsFromnote 2431747-GeneralLedger:IncompatiblechangesinS/4HANAcomparedtoclassicERPreleasesSeeattachmentreferencedtherein 2015_04_07_EKT_Architecture_final.pdfthefollowingisstated:DocumentNumberswithSimpleFinance2.0SincewewriteonlyonejournalentryforallofthecomponentsG/L,CO,AA,ML,onedocumentnumberissufficientfromabusinesspointofview.Thejournalentryconsistsoutofaheader(BKFP)anditems(ACDOCA).Therespectivedocumentnumber(BKPF-BELNR/ACDOCA-BELNR)obeysthe(legal)rulesofFinancials.Asaconsequence,thedocumentnumberisdependentofthefiscalyearandthecompanycode.COdocumentnumbershavenotbeenyeardependent.Materialledgerdocumentnumbershavenotbeendependentfromtheorganizationalunit(e.g.companycode).Bothnumbersdidnothavealegalrelevance.Forcompatibilityreasonsa“transactionnumber”isneededinCOandMLthathasthesametechnicalqualitiesthanthepreviouslyuseddocumentnumbers(e.g.monotonouslyincreasing).Moreover,ACDOCAhasa6digitfieldforthedocumentline,whereasCOEPhasonlya3digitfield,whichisusedinmanyuserinterfacesandreports.Forcompatibilityreasons,wehavetoofferanewtransactionnumberforevery999documentlines. RelatedDocuments:DocumentTypeDocumentNumberAssignmentNumberRangeinFinancialAccountingBufferingNumberRangesandLegalFrameworkNumberRangeGaps   RelatedSAPNotes/KBAs SAPNote1234302-ContinuousdocumentnumberallctninthenewgeneralledgerSapNote1828201-MissingdocumentnumbersforaccountingdocumentsSAPNote1398444-BufferingthedocumentnumberassignmentforRF_BELEG SAPNote504875-BufferingnumberrangesSAPNote 672255-Shortenedfiscalyear/changingfiscalperiodsSapNote 2431747-GeneralLedger:IncompatiblechangesinS/4HANAcomparedtoclassicERPreleasesSapNote 2371023-NumberRangeforML-DocumentinS/4FinanceOn-PremiseEditionSapNote 2376829-FAQ:BufferingfornumberrangeobjectRF_BELEGinS/4HANA     snrosnumnrivbufferingcheck_duprecs_in_tabmessage_type_xgi220 Overview ContentTools PoweredbyAtlassianConfluence7.4.14 PrintedbyAtlassianConfluence7.4.14 Reportabug AtlassianNews Atlassian Privacy TermsofUse LegalDisclosure Copyright Trademark {"serverDuration":181,"requestCorrelationId":"01813c8b11dd7528"}