Sequence No. not defined for the location [Message 80072-11]

Dear Friends,
I have setup sequence for A/R Invoice, Incoming / Outgoing Payment and Excise Register, and created a few document successfully (with sequence number). But when I go to u201CTax Payment wizardu201D, in the 2nd stage on selection of any location give the following error and even the u201CSeq. Nameu201D does not show any sequence name.
u201CSequence No. not defined for the location [Message 80072-11]u201D
Can any one please tell me the reason behind for SAP B1 2007B SP0 PL7?

Hi Narottam,
Check this link
Sequence Series
Regards
Jambulingam.P

Similar Messages

Err in PO creation-Sales document item is not defined for the transaction

Hi,
I am getting the following error while creating PO
"Sales document item 30000183 000100 is not defined for the transaction
Message no. V1 198
Diagnosis
You have tried to carry out a business transaction for this sales and distribution document item which, for this item, is not allowed.
This may be due to the fact that this item is not part of a make-to-order production with cost management in the sales order."
I have used an item category which is copy of TAB and the sales order line item is attached to WBS element.
can any one guide me what needs to be done.
thanks

If you want the sales order creation to initiate a PO creation automatically, check if the "Create PO Automatically" button is ticked on for the item category in Transaction flow tab in tcode VOV7
This will solve your problem, provided your configuration for PO on the MM side is fine.
Reward if this helps.

Special G/L indicator X is not defined for down payments (Message no. F505)

{{{ Special G/L indicator X is not defined for down payments
Message no. F5053
The specified special G/L indicator is not classified as "down payment" or not listed in the list of the target special G/L indicators for indicator "F".}}}
*I have Created the Indicator X for Downpayment, and even assign both account to it but when i try to make my transaction using F-47 , it give me this error... kindly Give me Solution.can any one tell me how i can see the of the target special G/L indicators for indicator "F" *
Full Points would be awarded
Regards

Hello Maz,
Please can you tell me the solution. I have the same problem with the following
Message no. F5053
The specified special G/L indicator is not classified as "down payment"
or not listed in the list of the target special G/L indicators for
indicator "F".
I have done all the settings in OBYR for Vendors and even included the Target sp.G/L ind 'Z' in my case for down payment request F.
Your help will be highly appreciated
Regards
Satish
EFI

SFLIGHT is NOT defined for the current logical database.

I have just started learning ABAP and bought an ABAP Objects book by Horst Keller. I have installed 4.6d mini sap and SAP GUI 6.4 on win XP Prof. I executed S_FLIGHT_MODEL_DATA_GENERATOR to load DB tables.
(1). When I tried to check a sample program, I get an error message SFLIGHT is not defined for the current logical database.
Here is the partial code:
REPORT zbcb01f1 .
TABLES: sflight, sbook.
DATA: BEGIN OF sr OCCURS 100,
      carrid LIKE sbook-carrid,
      connid LIKE sbook-connid,
      fldate LIKE sbook-fldate,
      bookid LIKE sbook-bookid,
      order_date LIKE sbook-order_date,
      loccuram LIKE sbook-loccuram,
      END OF sr.
GET sflight.   <---- Error is pointed here
(2). I am also not getting Graphical Screen Painter when selecting Layout for a screen. Instead, I am getting alphanumeric editor.
Someone please help me.
Raizak.

Hi Raizak,
the easiest way is to go to service.sap.com/notes and enter the note number. For this time I've copied the 2 notes below.
Best regards,
Christian
Symptom
The Graphical Layout Editor of the Screen Painter either does not start or terminates.Error message 37527 is displayed in the session in which the call was made (Graphical Layout Editor not available.
Additional key words
() EUNOTE, EUSCREENPAINTER, 37 527
Cause and prerequisites
This note comprises all the common causes for error message 37527 and provides you with information on how to systematically trouble shoot the problem.
1. Windows32 or UNIX/motif?
As of Release 4.6B there is only the program version for 32bit Windows (NT, 95, 98, 2000 ff.).Up to Release 4.6A there was also a version for UNIX/Motif.All of the more current notes (with the exception of Note 45490) refer only to the Windows version.
2. Termination at the start or during use?
The following diagnostic steps refer to the causes of the errors which prevent the Graphical Layout Editor from starting. However, there are also known error causes, which result in the program terminating when the application is being used and which also produce the 37527 error message. This affects -
Rel.4.6C/D: Termination when attempting to read texts in the logon language -> Note 375494
Crash after transferring program and dictionary fields. Termination after transferring program and dictionary fields -> Note 189245
Release 3.1I: Termination after inputting field text -> Note 113318
3. Is the SAPGUI installation correct?
The Graphical Layout Editor is automatically installed during the standard installation of the SAPGUI.If you chose a non-standard installation, then you should have explicitely selected its installation (component "Development Tools - Graphical Screen Painter").
The program executable is called gneux.exe.During the SAPGUI installation it is placed in the same directory as the SAPGUI programms (for example, front.exe) (usually C:\Program Files\SAPpc\sapgui). The following belong to the program:
- An additonal executable gnetx.exe (RFC starter program)
- the DLL eumfcdll.dll
- various eusp* data files (that is, the names all begin with eusp.)
You can check the completeness of the program installation by starting the program gneux.exe locally in the SAPGUI directory (for example, by double-clicking on the program name in the Explorer window).The Layout Editor is displayed with German texts and an empty drawing area for the pseudo screen EUSPDYND 0000.
If the installation is not complete, an error dialog box provides information regarding the cause of the error, for example, sometimes the DLL eumfcdll.dll is missing after reinstalling the SAPGUI. For example, the eumfcdll.dll DLL was sometimes missing after the SAPGUI was reinstalled.
4. System link defined and okay?
The Graphical Layout Editor is a separate program which is started by the Screen Painter Transaction (SE51) on the Frontend machine.
Up to Release 3.0F, the programs communicated with each other via the graphics log of the SAPGUIs (gmux).The definition of the environment variable SAPGRAPH may be the cause for the program not being being found where it is.
As of Release 3.1 G, the programs use a separate RFC link which is set up in addition to the SAPGUI's RFC link.Missing or incorrect definitions of the RFC destination EU_SCRP_WN32 or problems with the creation of the RFC link are the most frequent causes for error message 37527 being displayed.Below you can find the correct settings for the RFC destination EU_SCRP_WN32 (under "Solution").Note 101971 lists all the possible causes for problems with the RFC link set-up. Attention:The Graphical Layout Editor may not be operated through a firewall (for example between the SAP and the customer system) because this does not allow an additional RFC connection in addition to the SAPGUI.
Solution
ad 1 UNIX/Motif
Note 45490 describes possible errors resulting from an incorrect program installation under UNIX/Motif (up to Release 4.6A).
ad 2 Termination when using
The above-mentioned notes may contain options for solving individual problems.However, you usually have to replace the program with an corrected version.You can do this either by downloading a patch from sapservX or by installing a more current SAPGUI.The patch is mentioned in the respective note.
ad 3 Installation
You either need to reinstall the SAPGUI or manually copy the missing file into the SAPGUI directory.In both cases you should make sure beforehand that a Graphical Layout Editor is no longer running.To do this you can either remove all processes gneux.exe from the process list by using a tool such as Task Manager (on WindowsNT) or exit the Graphical Layout Editor from the Screen Painter Transaction menu via Edit -> Cancel Graphical Screen Painter). Attention:For each session or system an individial Layout Editor process may exist so that, if need be, several processes should be cancelled.
ad 4 System link
Up to Release 3.0F:you can either delete the environment variable SAPGRAPH or copy all the files of the Graphical Layout Editor into the directory which is specified by SAPGRAPH.
As of Release 3.1G:you can use Transaction SM59 to check the RFC destination EU_SCRP_WN32 (expand the TCP/IP connections, select destination EU_SCRP_WN32).If the destination is missing, then you should create it with the following settings:
- Connection type "T" (start of an external program via ...)
- Activation type "Start"
- Start on "Front-end workstation"
- Front-end workstation program "gnetx.exe" (caution! NOT gneux.exe)
- Description (optional) "Graph. Screen Painter (Windows32)
Start Program gneux.exe using the gnetx.exe starter program."
If you want to start the program from a different directory than the SAPGUI standard directory, then replace the default value under Frontend work station by the complete path name for program gnetx.exe.Transaction SM59 also allows you to check the RFC connection via the pushbutton "Test connection").In this case the system attempts to localize and start the program gnetx.exe.If there are errors, a message is displayed regarding the possible causes (for example, gateway problem, timeout problem or the like).Note 101971 provides a detailed explanation of the problems involved with an RFC connection set-up.As the Graphical Screen Painter requires a functional RFC connection as of Release 3.1G, contact the System Administrator or create an message on the topic Middleware (BC-MID-RFC) if you encounter RFC problems.
If the program gnetx.exe can be found and started, the banner dialog box with logo, release data and version number is displayed briefly.As the Layout Editor itself is not started, the error cause must be in the installation of the Layout Editor program gneux.exe if the connection test was successful.
Release 4.5A to 4.6B: Use with Releases <3.1G>.
The Graphical Layout Editor is downward-compatible as regards the system connection, that is, an RFC-based Layout Editor for example from Release 4.6C can also be used on a non-RFC-based Screen Painter, for example of Release 3.0F.However, the releases mentioned above have a program error which causes a crash due to memory violation in the start phase of the program.Note 197328 describes the solution by installation of the corrected program version.
Important: Trace file dev_euspNNN!
If none of the diagnosis steps leads to the cause of the error and to the solution of the problem via the corresponding note, then you should add the contents of the trace files dev_euspNNN (NNN = process number) to the message for SAP, if possible.You can find this file in the current directory of the SAP System, for example under Windows NT in C:\Winnt\Profiles\<user>\SAPworkdir.If several such trace files can be found there, make sure that you use the file which matches the termination time with respect to date and time of creation.In most cases the ERROR message in the last lines of this trace file provides an important note on the cause of the error.
Source code corrections
Symptom
The graphic layout editor of the Screen Painter cannot be started (RFC version).
Other terms
() EUNOTE, EUSCREENPAINTER
Reason and Prerequisites
This is generally caused by the fact that the RFC connection between the frontend graphics layout editor and the calling screen painter program at the backend cannot be set up.
Possibility 1: Route permission denied
In the trace file dev_eusp<Process Id> of the graphics layout editor you find the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR route permission denied (<Front-Id> to <BackId>,<Service>)".
If there is a firewall between frontend computer and application
server, you need to decide whether the port for the RFC of the graphical layout editor can be released here (see Solution 1 below).
In case no firewall exists between the frontend computer and the application server, in its route permission table, the SAProuter contains either no entry for the frontend computer, on which the graphics layout editor is started, or the entry says that the link is saved by a password.Since the connection is denied, the graphics editor processes exits again, and the screen painter switches to the alphanumeric layout editor.
Possibility 2: Service 'sapgw<ServiceId>' unknown
In the trace file dev_eusp<ProzessId> of the graphics layout editor you have the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR service 'sapgw<ServiceId>' unknown".
The service sapgw<ServiceId> (for example, sapgw00) is not known on one of the computers participating in the RFC communication because the corresponding entry is missing in its service file. The affected computer can be the frontend computer or the gateway computer.
Possibility 3: The system parameter gw/cpic_timeout value is too low
This system parameter determines how many seconds the gateway is waiting for the RFC connection to be set up.In case of a high network load, the default value of 20 seconds is too small with the result that the connection cannot be created on time.Here the graphics layout editor process also exits with the trace file entry "ERROR in RFCMgr_accept: not accepted".
Possibility 4: System parameter abap/no_sapgui_rfc set
The profile parameter abap/no_sapgui_rfc of the system is set (that is, it has a value not equal to space or 0).This prevents the program of the graphics layout editor from being started with RFC at the frontend.
Possibility 5: Unnecessary authorization check
The error message "No RFC authorization for user xxxxxx" is generated although the check of the RFC authorization was deactivated by profile parameter auth/rfc_authority_check (value = space or 0). The problem is caused by a program error, that ignores the value of the profile parameter let during the call of the RFC authorization check (see Note 93254). This error can occur as of Release 4.5.
Solution
ad 1) If a Firewall is installed between frontend computer and the application server, you need to decide whether the port for the RFC link of the graphical layout editor shall be released in the firewall. This is port 33nn, where nn is the 2-digit system number of the SAP application server. As of Release 3.1G, the graphical layout editor needs an RFC link for communication with the application server in addition to the already existing linkof the SAP GUIs. Such a second link is not allowed by the firewall in general because it would contradict the security concept (password protection, logging of the connection).
If no firewall exists, you should check whether the frontend computer can be added to the route permission table or whether the password option can be removed from out of the available entry.
For details refer to chapter 4.4 of the attached Note 30289.
ad 2) Include service sapgw<ServiceId> in the service file.
Refer to Note 52959 for details.
ad 3) Increase value for system parameter gw/cpic_timeout. 60 seconds should be sufficent as a timeout limit.
ad 4) Set the system parameter abap/no_sapgui_rfc to space or 0
Start the application server so that the new parameter value comes into effect.
ad 5) Import the Support Package specified in the attachment for the release in question or implement the advance correction in the source code as described in the attached correction instructions.
As a workaround, assign RFC authorizations as described in Note 93254.

"PERNR" is not defined for the current logical database.

Hi Experts,
I have developed a program for HR salary variance but when i execute i getting error in the line " get PERNR"
the "PERNR" is not defined for the current logical database. so plz suggest me to avoid this issue.
Thanks,
Rajesh

the codes are has below,
*& Report ZHRSAL_COMP
REPORT ZHRSAL_COMP.
tables: pernr,
        t512t.                      "Wage type texts
infotypes: 0001. "Organizational Assignment
*Tables data containing directory to PCL2 payroll results file.
data: begin of rgdir occurs 100.
        include structure pc261.
data: end of rgdir.
data: result type pay99_result.
data: rt_header type line of hrpay99_rt.
data: country like t001p-molga,
      number like pc261-seqnr. "Number of last payroll result
types :begin of struc_p0001,
       pernr type p0001-pernr,
       ename type p0001-ename,
       werks type p0001-werks,
       btrtl type p0001-btrtl,
end of struc_p0001.
data : gtab_p0001 type table of struc_p0001,
       gwa_p0001 type struc_p0001.
types : begin of struc_payroll,
        text(10) type c,
        date     type dats,
        month(2) type c,
        year(4) type c,
        abkrs(2) type c,
        end of struc_payroll.
data : gtab_payroll type table of struc_payroll,
       gwa_payroll type struc_payroll.
types : begin of struc_result,
       lgart type lgart,
       lgtxt type t512t-lgtxt,
       betrg type betrg,
        end of struc_result.
data : gtab_result type table of struc_result,
      gwa_result type struc_result.
get pernr.
rp_provide_from_last p0001 space pn-begda pn-endda.
call function 'CU_READ_RGDIR'
    exporting
      pernr          = p0001-pernr
    importing
      molga           = country
    tables
      in_rgdir        = rgdir
    exceptions
      no_record_found = 1
      others          = 2.
if sy-subrc = 1.
    write: / 'No records found for '(001), pernr-pernr.
endif.
call function 'CD_READ_LAST'
    exporting
      begin_date      = pn-begda
      end_date        = SY-DATUM
    importing
      out_seqnr       = number
    tables
      rgdir           = rgdir
    exceptions
      no_record_found = 1
      others          = 2.
if sy-subrc = 1.
    write: / 'No payroll result found for'(002), pn-paper.
else.
    call function 'PYXX_READ_PAYROLL_RESULT'
         exporting
              clusterid                    = 'RX'
              employeenumber               = p0001-pernr
              sequencenumber               = number
        READ_ONLY_BUFFER             = ' '
        READ_ONLY_INTERNATIONAL      = ' '
        CHECK_READ_AUTHORITY         = 'X'
   IMPORTING
        VERSION_NUMBER_PAYVN         =
        VERSION_NUMBER_PCL2          =
         changing
              payroll_result               = result
         exceptions
              illegal_isocode_or_clusterid = 1
              error_generating_import      = 2
              import_mismatch_error        = 3
              subpool_dir_full             = 4
              no_read_authority            = 5
              no_record_found = 6
              versions_do_not_match        = 7
              others                   = 8.
    if sy-subrc = 0.
      perform print_rx.
    else.
      write: / 'Result could not be read (003)'.
    endif.
endif.
      FORM PRINT_RX                                        *
      Print Payroll Result                                 *
form print_rx.
format intensified on.
write: / p0001-pernr,
           p0001-ename(15),
           p0001-werks,
           p0001-btrtl.
format intensified off.
skip 1.
move p0001-pernr to gwa_p0001-pernr.
move p0001-ename(15) to gwa_p0001-ename.
move p0001-werks to gwa_p0001-werks.
move p0001-btrtl to gwa_p0001-btrtl.
append gwa_p0001 to gtab_p0001.
write: / 'For period/payroll area: '(004),
           30 result-inter-versc-fpper+4(2),
           result-inter-versc-fpper+0(4),
           result-inter-versc-abkrs,
           / 'In-period/payroll area: '(005),
           30 result-inter-versc-inper+4(2),
           result-inter-versc-inper+0(4),
           result-inter-versc-iabkrs.
skip 1.
gwa_payroll-text = 'For'.
move result-inter-versc-fpper to gwa_payroll-date.
move result-inter-versc-fpper+4(2) to gwa_payroll-month.
move result-inter-versc-fpper+0(4) to gwa_payroll-year.
move result-inter-versc-abkrs to gwa_payroll-abkrs.
append gwa_payroll to gtab_payroll.
gwa_payroll-text = 'In'.
move result-inter-versc-fpper to gwa_payroll-date.
move result-inter-versc-inper+4(2) to gwa_payroll-month.
move result-inter-versc-inper+0(4) to gwa_payroll-year.
move result-inter-versc-iabkrs to gwa_payroll-abkrs.
append gwa_payroll to gtab_payroll.
write: 'Results table: '(006).
skip 1.
loop at result-inter-rt into rt_header.
    perform re512t using result-inter-versc-molga
                         rt_header-lgart.
    write: / rt_header-lgart,
             t512t-lgtxt,
             rt_header-betrg currency rt_header-amt_curr.
move rt_header-lgart to gwa_result-lgart.
move t512t-lgtxt to gwa_result-lgtxt.
move rt_header-betrg to gwa_result-betrg.
append gwa_result to gtab_result.
endloop.
endform.                    "print_rx
      FORM RE512T                                          *
      Read Wage Type Texts
form re512t using value(country_grouping)
                  value(wtype).
check t512t-sprsl ne sy-langu
     or t512t-molga ne country_grouping
     or t512t-lgart ne wtype.
select single * from t512t
              where sprsl eq sy-langu
              and   molga eq country_grouping
              and   lgart eq wtype.
if sy-subrc ne 0.
    clear t512t.
endif.
endform.                                                    "re512t

Sales document item is not defined for this transaction in Pur.Order

hi,
At the time of convertion of pr to po one error message received.
Sales document item 46 000010 is not defined for the transaction
Message no. V1198
Diagnosis
You have tried to carry out a business transaction for this sales and distribution document item which, for this item, is not allowed.
This may be due to the fact that this item is not part of a make-to-order production with cost management in the sales order.
Procedure
Please check your entries.
this is MAKE TO ORDER SCENARIO THIS ERROR IS FOR RAW MATERIAL CONVERTION AGAINST SALES ORDER.

Hi,
Check in material master MRP3 view there is field called strategy group where you have option to define the planning strategy like make to order/make to stock & like.
Regards
Ravi Shankar.

ERROR in MIRO : An exchange rate type is not defined for country IN

Experts:
When I try to enter the invoice received from the vendor, I am getting the following message.
An exchange rate type is not defined for country IN
Message no. FF802
Can anyone provide me a solution for this?
Thanks,
Vijai

This is the explanation given in note 974619 for the above error message
Summary
Symptom
When you post an FI document, the system issues error message FF 801 or FF 802.
Other terms
Plants abroad, FF 801, FF802
Reason and Prerequisites
You use the 'Plants abroad' function.
See Note 882132 for more information about this.
Solution
If the 'Plants abroad' function is active, additional fields appear when you maintain the country global parameters (transaction OY01, table T005):
- Country currency       (Field WAERS)
- Exchange rate type     (Field KURST)
- Net discount base      (Field XSKFN)
- Net tax base           (Field XMWSN)
You must maintain the fields 'Country currency' and 'Exchange rate type'.
Otherwise, the system issues error message FF 801 or FF 802.
thanks
G. Lakshmipathi

Error: "posting period is not defined for fiscal year variant" in FBICS3

Hi,
I got error "posting period is not defined for fiscal year variant" when I execute t code FBICS3.
I checked in OB29 & t code FBIC010 & noted that the fiscal year variant had ben maintained.
Please advice.

HI,
It was noted that the mentioned t code had been maintain but below mentioned error appear:
Posting period is not defined for fiscal year variant
Message no. GU506
Diagnosis
You have tried to determine a posting date in fiscal year variant for period , fiscal year , but this period is not defined for the variant.
Procedure
You maintain fiscal year variants in table T009.
It was referring to t code OB29. I have checked the detail, in OB29 also details maintain.
Please advice why the error still prompt.

Error as unit of measure PC not defined for language RO while creation ofPO

Hi GUYS,
When am trying to create a PO in ME21N transaction i got error as below,
unit of measure PC not defined for language RU
Message no. 06079
Table 006A contains no entry for this unit of measure
Please let me know what action to be taken from my side to over come this issue.
Note: If i check the related vendor i could able to view that the language maintained as RU.
Cheers,
Kumar.S

Hi Jurgen,
Thanks for your reply once again.
As mentioned by you earlier i have tried to login with languae RU in Q system but unfortunately i got an error saying taht language not installed.
Also we found for Language - EN and UOM - PC has been maintianed in T006A table.But if i check for lanugage - RU and UOM PC combinatoin has not manintaned in T006A table.
Please let me know how to maintain the values in this table T006A for combination Lang - RU and UOM - PC.
Please revert back with your soilution.
Note: I have tried in SM30 but failed due to below error
The maintenance dialog for T006A is incomplete or not defined
Cheers,
Kumar.S

Tax category DE 2 is not defined for country 1

Hi to all,
We are in retail project while changing the article master following data is coming automatically to tax data in general data DE Germany MWST Output Tax O Unbranded Other. When I save the article master, i am getting following error.
Tax category is not defined for country DE
Message no. M3019
Diagnosis
The combination of values you have entered is not defined in the system.
Procedure
Check your entries, and choose a valid value or combination of values with F4.
If you want the value(s) to be defined in the system, contact your systems administrator.
Detail error E M3 019 : Tax category DE 2 is not defined for country 1
Regards
Govind

Hi Anil,
Allready it was maintained
Regards
Govind

Tax Jurisdiction Code not defined for procedure TAXSE

Hello,
We are facing any issue with the error "Tax Jurisdiction Code not defined for procedure TAXSE"
We are in mid of production bill run and this is getting very critical. Any pointers would be highly appreciated.
The company code country is SE (Sweden)
We have 2 BPs with address in California, US.
The Billing is successful for both the BPs.
While invoicing, one BP is successful.
The other is going in error "Tax Jurisdiction Code not defined for procedure TAXSE".
Error Details
Jurisdiction code not defined for procedure TAXSE
Message no. FF748
Diagnosis
You have entered a jurisdiction code in a country whose calculation procedure
does not allow the entry of jurisdiction codes.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system
settings.
To do this, choose Maintain entries (F5).
Change your calculation procedure so that tax calculation is carried out
using the jurisdiction code.
The BP and the CA setup is exact for both the cases.
Thanks

Hi
Go to the following SPRO config-
SAP Customizing Implementation Guide-->Financial Accounting-->Contract Accounts Receivable and Payable--->Basic Functions--->Contract Accounts--->Field Modifications--->Configure Field Attributes per Activity
Select Change and double-click on field grouping Jurisdiction code.
You will get the following screen.
You have to tick the option Changes plannable and then you will be able to remove jurisdiction code from CAA2
Hope it helps..
Thanks,
Amlan

Special G/L indicator H is not defined for down payments

Can Any body help me please... I am giving the error details when i am posting Speical GL in F-37. Actually i want to post a Security Deposit made against Customer.
Special G/L indicator H is not defined for down payments
Message no. F5053
Diagnosis
The specified special G/L indicator is not classified as "down payment" or not listed in the list of the target special G/L indicators for indicator "F".
System Response
The entry is not accepted.
Procedure
Enter an allowed special G/L indicator or initiate a change of the default settings.
Thank you in advance

Hello,
In FS00 we will create the gl account for advance in control tab specifying vendor or customer.
next we will come to OBYR (vendor special transactions)
here first you have to define the special gl indicator SAP predefined some special gl indicators but if u want to create a new one first you have to create and in next tab you will attach vendor reconciliation and special gl account created in FS00 for advances.
in case if u want to create a special gl indicator for customer go to OBXR do the same as above.
specail gl indicators created in OBYR or OBXR are not work in FB60 or FB70 to book bills.
Hope this is clear, in case of query revert back.
Regards,
sankar

Special G/L indicator L is not defined for down payments

Hi,
While i am doing in the F-47 transaction i am trying to post down payment then i am getting the following error : --
Special G/L indicator L is not defined for down payments
Message no. F5053
Diagnosis
The specified special G/L indicator is not classified as "down payment" or not listed in the list of the target special G/L indicators for indicator "F".
Regards,
Rajesh

Hi
This error is due to non-assignment of G/L Accounts.
Go to OBYR or FBKP and double click sp. g/l. indicator F for Vendor type K and assign Reconciliation account and sp. g/l. account(advance to Vendors account) and save.
Also for sp. g/l. indicator L you might have done this as that Indicator you are using for Down Payments
and sp. g/l indicator F for Requests.
Regards
Venkat
Edited by: Venkat Dara on Jun 6, 2009 2:44 PM

Licence is not included for the material - J1IH

Hi All
We are working on ECC 6.0.
While doing J1IH ( Additional Excise) with Subtransaction Type 01, we are getting a warning message as -
Licence is not included for the material
Message no. 8I993
However if we process without any Subtransaction Type, no warning is flashed.
Please let me know the reason for the same and what could be done so that system doesnt prompt it?
Regards
Kapil

Hi
Check SAP note 1223591
Regards
Antony

Unit of measure not defined for language ZH

Hi,
We were creating a PO when we encountered the error which states "Unit of measure not defined for language ZH".
We executed CUNI to translate the units of measurement to our target language. System prompted "This object was segmented. Only new lines evaluated." What does this mean?
We tried creating the PO again, however we encountered the same error that the unit of measure was not defined for the language.
Please recommend action/s that we should take. Thank you.

Take a look at the below threads. Your problem has the solution.
Re: Unit of measure XX not defined for language DE
Re: Unit of Measure Error in Purchase order

Sequence No. not defined for the location [Message 80072-11]

Similar Messages

Maybe you are looking for