TO is unble to confirm with T-code LM02

Hi,
When the Storage Unit number is entered into LM02 (F4 Nxt) the transaction returning with a message
No To items to be confirmed.
However, This storage unit number contains TO items, which are waiting for confirmation in the system.
Any Idea?
Regards,
Ajinkya

Hi,
It is bit difficult to find the root cause with the provided information hope the below information will help
If destination storage type is a non SU managed (916), the SU is not found in SU table LEIN but the SU should be in the TO table
LTAP in the source storage type VLENR.
If the SU is not found in the source storage type of the TO table then it is a non existing SU and system throw error message

Similar Messages

I am qualified for the free version of lion...once I took a snap shot of my proof of purchase, it said it would send me a confirmation email with a code and it never did?

I am qualified for the free version of lion...once I took a snap shot of my proof of purchase, it said it would send me a confirmation email with a code and it never did?

You will get a .pdf file with the Redemption Code in it in your registered email inbox. You will have to enter the Redemption Code into the Redeem link on the right in App Store.
You will also receive an additional email with a password to open the .pdf file from the first email.
Enter the password to .pdf file > Copy the redemption code and enter it in App Store > Enter your Apple ID and password in the App Store pop-up > Poof!!! Magic! Your OS X Lion icon shows up in your dock and the download begins!

Procedure Confirmed with Comparing Dates

Trying to compare two dates, and there's so many ways I'm
just getting a bit
confused.
I have a date stored in my database in a timestamp field with
this format:
2006-03-05 19:13:05
I have a term defined in months (in the database) of how long
the account is
valid:
term: 12
I can now almost get the expired date, with this code, where
$vDate is the
untouched date from my database, and $term is the term in
months.
$blog2 = date("M jS Y",strtotime($vDate,'+'.$term.'
Month'));
But it only increments the months, not the years.
Now, here's my problem:
I can create an array with expired and current dates, but
then I have to
construct a moderately complex if/elseif statement to check
year, then
month, then day.
Is there a better way? IE, can anybody think of a method in
which I can
compare the dates more efficiently? I'm going in circles.
Everytime I
think I've almost got it, I lose something.
Any suggestions?
TIA,
Jon

David, thank you for replying.
I was just looking at doing it with SQL, but here is my
question/problem:
I am doing this for a client database of hosting customers -
a one-stop list
so we can see who's due. I'm worried about having two sql
queries per
customer. Currently it wouldn't be a big deal, but hopefully
in the future
it would be.
Can you confirm this would be an issue? If it is an issue,
can you take a
peek at my code below? Can you confirm I'm either bass
ackwards or on the
right track to do this in PHP? As I stated, if there's an
easy SQL solution
that won't cause extra load on the server, cool.
I'm doing it as such now (my previous method was not
working):
$dates1 = create_Dates($renewDate);
//Create_dates function listed below
$status = account_expire($dates1);
echo $status;
//account_expire function below:
//Create Dates function:
function create_Dates($date){
$date = strtotime($date);
$dates['eM'] = date("m",$date);
$dates['eD'] = date("j",$date);
$dates['eY'] = date("Y",$date);
$dates['cM'] = date("m");
$dates['cD'] = date("j");
$dates['cY'] = date("Y");
return $dates;
//and this long bore is my if/else to check dates:
function account_expire($dateAray){
//exploding an array would be best
$eM = $dates['eM'];
$eD = $dates['eD'];
$eY = $dates['eY'];
$cM = $dates['cM'];
$cD = $dates['cD'];
$cY = $dates['cY'];
//this is where we begin calculating
if($eY > $cY){ //07 > 06
$status = 'Paid';
return $status;
elseif($eY < $cY){
$status = 'EXPIRED';
return $status;
elseif($eY == $cY){
if($eM > $cM){
$status = 'Paid';
return $status;
elseif($eM < $cM){
$status = 'EXPIRED';
return $status;
elseif($eM == $cM){
if($eD > $cD){
$status = 'EXPIRED';
return $status;
elseif($eD <= $cD){
$status = 'Paid';
return $status;
>
> Use the MySQL DATE_ADD() function:
>
>
http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html
>
> SELECT registered, DATE_ADD(registered, INTERVAL 12
MONTH) AS expiry
> FROM myTable
>
> If your expiry dates are always 12 months ahead, that
can be hard coded
> into your SQL. If the terms are variable, do a SELECT
query first to get
> the term, then do a second query using the first result.

[ForumFAQ]How to troubleshoot error "SSPI handshake failed with error code 0x80090324"

Understanding the problem:
When connect to SQL Server with Windows authentication, you may receive the following message in the SQL Server error log:
SSPI handshake failed with error code 0x80090324, state 14 while establishing a connection with integrated security; the connection has been closed.
Security Support Provider Interface (SSPI) is a set of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. SQL Server supports Kerberos indirectly through the Windows Security Support
Provider Interface (SSPI) when SQL Server is using Windows Authentication.
"SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos Authentication. There are many reason for SSPI Handshake error to appear in SQL Server error log.
Troubleshot the problem:
Download and install the Windows error code lookup tool Err.exe to view error descriptions for Windows Error Codes.
The error code 0x80090324 (SEC_E_TIME_SKEW) means "clock on client and server machines are skewed". In most case, this is a Kerberos issue. Kerberos is using a timestamp to protect against replay attacks. The maximum time skew that can be tolerated
between a ticket's timestamp and the current time at the KDC is 5 minutes by default.
Also check the Windows Event Log of client machine, domain controller and the SQL Server machine for existence of W32time error messages.
The solution:
Make sure the clock of client server, domain controller and the server running SQL Server are within five minutes of each other. Or Resynchronize the clock by run w32tm /resync on client machine and SQL Server machine.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This error can happen due to Active Directory configuration issue or Network related issues. Assuming they are fine,
another reason could be related to fail Kerberos Authentication to connect to SQL Server.
In Windows 2003 and above, the default method of establishing a connection is Kerberos but if it fails, then connection may be established using NTLM. An error may be registered on SQL Server error log due to Kerberos failure.
To confirm if you have any database connection using Kerberos authentication, run this on your SQL Server
SELECT distinct auth_scheme FROM sys.dm_exec_connections
If you only see NTLM and SQL then, there is no Kerberos connection.
To use Kerberos, the client and SQL Server must be in the same domain or trusted domains and a Service Principal Name (SPN) must be registered with Active Directory for SQL Server service account.
You can check if the service account already has SPN, by running this on the SQL Server
setspn -l <domain\sqlserviceaccount>
If you don't see anything starting with MSSQLSvc\ then the account is not setup with SPN.
You can manually register SPN as a Domain Administrator using these commands.
To create an SPN for the NetBIOS name of the SQL Server use the following command:
setspn –A MSSQLSvc/<SQL Server computer name>:1433 <Domain\Account>
To create an SPN for the FQDN of the SQL Server use the following command:
setspn -A MSSQLSvc/<SQL Server FQDN>:1433 <Domain\Account>
If SQL Server service account is granted "Validated write to service principal name" privilege in Active Directory, SQL Server database engine will register itself when it starts and unregisters at shutdown. If you Domain Administrators do not permit this setting
then you should manually register the SPN and the SSPI error will go away.
Also the SQL Server service account must be granted "Account is trusted for delegation" privilege in Active Directory. If your SQL Server connects to other SQL Server using Linked Server then the server must also be granted "Trust this computer for delegation
to any service" privilege.
For a named instance, you can use the FQDN of the named instance instead of SQL Server FQDN and use the port number.
For a clustered server, you should use the FQDN of the SQL Server virtual name. In this case you will need two entries, one with port name and one without such as
setspn -A MSSQLSvc/<Virtual SQL Server FQDN> <Domain\Account>
setspn -A MSSQLSvc/<Virtual SQL Server FQDN>:1433 <Domain\Account>
Kerberos authentication works when SQL Server, Service Account and Windows account accessing the SQL Server are in same windows domain. If anyone these are in different domain, there must be bidirectional trust established between the domains, otherwise it
does not work.

PO Confirmations with Multiple Line items

Hi Experts,
In our Business Scenario, the Purchase Order Confirmations are being received by IDoc from Vendors. IDoc Basic Type is ORDERS01.
Issue is when we have one PO line item, then the IDoc is getting processed successfully. But when we have Multiple PO line items, then the IDoc is failing with the following error
Material number differs from that of ordered material 000000000001797950
Message no. ME790
Diagnosis
The acknowledgment/confirmation for purchase order no. 8195817140 with item 00002 cannot be adopted because the customer material number from the IDOC differs from the material number 000000000001797950 from the PO.
Procedure
Either change the customer material number in the IDOC or get the vendor to send a new acknowledgment/confirmation with the correct material number.
There is no control observed in the Material. For the second line item of the PO it is happening. If this Material is a first line item in the PO, then this issue won't be there.
Request for your inputs please
Thank you,
Best Regards,
Ramakrishna Mangena

Hi,
Use T code WE60 to search for the segment documentation of IDoc type
IDoc needs three different kinds of segment types:
E1EDK01 is the main segment of an ORDERS01 IDoc.Used for calling program to pass the SAP IDoc syntax check.
E1EDP01 is the segment for a single order position. The field MENGE contains the quantity. Of course, this segment can occur more the once.
E1EDP19 represents an object definition. In this case the object is a material number. The field QUALF is therefore set to 002 and the material number is written into the IDTNR field. E1EDP19 segments are always children of E1EDP01
Thanks & regards,
ShreeMohan

ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function

Hello,
I am calling a windows bat file using dbms_scheduler and getting the following error. I have searched the forum and the internet and tried different switches and options. None of them solved my problem.
Oracle Version: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
OracleJobScheduler is running as a service
Error starting at line 1 in command:
execute GET_RESULTS();
Error report:
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
ORA-06512: at "SYS.DBMS_ISCHED", line 185
ORA-06512: at "SYS.DBMS_SCHEDULER", line 486
ORA-06512: at "PS.GET_RESULTS", line 67
ORA-06512: at line 1
27369. 00000 - "job of type EXECUTABLE failed with exit code: %s"
*Cause:    A problem was encountered while running a job of type EXECUTABLE.
The cause of the actual problem is identified by the exit code.
*Action:   Correct the cause of the exit code and reschedule the job.
Here is the code for scheduler
      dbms_output.put_line(os_commandline || utlPath || fileSeparator || 'get.bat >nul')
      dbms_scheduler.create_job
      (   job_name          =>'PS_GET_RESULTS'
            , job_action        => os_commandline || utlPath || fileSeparator || 'get.bat >nul'
            , job_type          =>'executable'
            , enabled           =>false
            , auto_drop         =>false
            , start_date        =>systimestamp
      dbms_scheduler.run_job(job_name =>'PS_GET_RESULTS');The dbs_output prints a line which shows that the parameters os_commandline, utlPath and fileSeparator are set correctly.
     C:\windows\system32\cmd.exe /q /c E:\UTLDir\get.bat >nulThe windows file (get.bat) is:
     "C:\Program Files (x86)\WinSCP\Winscp.exe" /script=e:\utldir\get_resultsThis batch file passes a script file to the executable winscp.exe to get files from another server.
The script file (get_results) is:
     option batch abort
     option confirm off
     open sftp://username:password@ipnumber:port -hostkey="ssh-rsa 1024 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
     cd /usr/dropbox/
     option transfer binary
     get *.results E:\UTLDir\Results\
     close
     exitI tested the batch file directly and works fine and "gets" the files from the server. But, invoking from Oracle dbms_scheduler fails with ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
Appreciate your help and time in suggesting additional guidelines or pointers.
Thanks,
Rose

Here is an update, if somebody else is having a similar problem.
The ftp command "cd" to change the directories should be an absolute path. I was given a path "/usr/dropbox/", but on the server it actually corresponds to "/usr/local/apps/dropbox/". After updating the directory path, the scheduler worked fine in invoking the batch file for transferring the files.
Thanks,
Rose

Collective order confirmation for particular codes

Hi
I have problem for some material codes while production order confirmation.The material codes that starts with Sxxxxxxxxxxxxxx this number are not getting confirmed. Others are get confirmed without any issue.
Production order confirmation is not working for that particular material code.
Please guide me what solution should I give to the customer.
BR
Sagar

Hi
This is the error message. and one more thing this is a collective order and this is happening for parent order while child order is confirmed correctly.Goods movement is done through CO27 and confirmation is done with CO11
BR
Sagar

User Exit for Production Order confirmation with CO15

Hi All,
what User Exit I should use when validating batch when we do Production Order confirmation with CO15.
Not when we create or release a Production Order.
Will reward,
mindaugas
Edited by: Mindaugas Kazlauskas on Jan 30, 2008 5:03 PM

Hi
The Follwing Userexits available:
    Transaction Code - CO15                     Enter Production order Confirmation
Enhancement/ Business Add-in            Description
Enhancement
CONFPP01
PP order conf.: Determine customer specific default values
CONFPP02
PP order conf.: Customer specific input checks 1
CONFPP03
   PP order conf.: Cust. specific check after op. selection
CONFPP04
    PP order conf.: Customer specific input checks 2
CONFPP05
   PP order conf.: Customer specific enhancements when saving
CONFPP06
   PP Order Confirmations: Actual Data Transfer
CONFPP07
   Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01
   PS confirmation: Determine customer specific default values
CONFPS02
PS confirmation: Customer specific input checks 1
CONFPS03
    PS confirmation: Customer specific check after op. selection
CONFPS04
   PS confirmation: Customer specific input checks 2
CONFPS05
   PS confirmation: Customer specific enhancements when saving
CONF0001
Enhancements in order confirmation
CONFPI01
   Process order conf.: Calculate cust.specific default values
CONFPI02
   Process order confirmation: Customer spec. input checks 1
CONFPI03
   Process order conf.: Cust. spec. check after op. selection
CONFPI04
   Process order conf.: Customer specific input checks 2
CONFPI05
   Process order conf.: Cust. spec. enhancements when saving
CONFPI06
Process order confirmation: Actual data transfer
CONFPM01
    PM/SM order conf.: Determine cust. specific default values
CONFPM02
    PM/SM order confirmation: Customer specific input checks 1
CONFPM03
PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04
   PM/SM order conf.: Customer specific input check 2
CONFPM05
   PM/SM order conf.: Cust. specific enhancements when saving
If it is helpful rewards points.
Regards
Pratp.M

CIN Study material with t-codes

Sir plz send me a link from which i will get complite CIN study material with t-codes.

Hi,
CIN is Country Version India
A Country Version is designed specifically to cater the business operations of that country over and above the generic SAP system functionalities. It comprises of functionalities degined for the laws and business practices pertaining to the country.
Most of the country-specific functions for India relate to Financials and Logistics.
The main areas are as follows:
Excise duty and the central value-added tax system (CENVAT)
Withholding tax (also known as tax deducted at source)
Sales tax
Maintenance and printing of statutory excise registers
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing scenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Here is some information on CIN Configuration. While it may not appear understandable as given below, it will be understood better when you check on screen.
Country Version India comes with four pricing procedures as follows:
JINFAC (Sales from manufacturing plants)
JINEXP (Export sales)
JINDEP (Sales from depots)
JINSTK (Stock transfers
CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID and state:
Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
The maximum number of items to be printed on each excise invoice
Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise Duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
? Specify whether it is a manufacturing site or a depot.
? Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, Multiple credit
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
Maintain Series Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
? Define excise series groups based on type of outgoing document
? Assign series group to excise registration ID
? If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
? If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
? If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
? If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
? Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
? Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
? Specify the conditions in the sales order that are used for excise rates.
? Specify the countervailing duty condition type used for import purchase orders.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
You maintain the following types of data:
? Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
? Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
? Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
? Material master data
Each material is assigned a chapter ID.
? Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Let's assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
? For taxes on purchases, use the condition types contained in the tax procedure.
? For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
? VS1 (basic excise duty)
? VS2 (additional excise duty)
? VS3 (special excise duty)
? VS5 (sales tax setoff)
? MWS (central sales tax)
? MW3 (local sales tax)
? ESA (service tax)
? ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
? Excise group
? Company code
? Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
? Defined the G/L accounts
? Defined the excise groups
? Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related subscreen appears.
Back to ERP Operation Home.
Transaction Codes for India
Transaction
Action
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challans
J1IFR
List subcontracting challans
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Hope this will help.
Rewad Point if helpful.
thanks,
Raja

Transport control program tp ended with error code 0212

Hi all,
I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
 service: transport service
 start : online
 Function: TMS_TP_SHOW_BUFFER
 message: TP_REPORTED_ERROR
In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
Can you tell me how to resolve this issue?

dev_tp contains:
This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
unicode enabled version
usage: R3trans.exe [<options>] <control_file>
The control_file describes what R3trans has to do.
The following options are possible:
-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d : DB connect. Test if SAP database is available.
-i file : Import from file without using a control file.
-l file : List the contents of file to the log file.
-m file : List the contents of file to allow tp to create a cofile.
-t : Test. All database changes are rolled back.
-t4 : Trace level 4. Switch on developer trace.
-u <int> : Unconditional modes. See below.
-v : Verbose. Write more details to the log file.
-w file : Log file. The default log file is 'trans.log'.
-x : DB connect without access on any SAP table.
R3trans.exe finished (0012).
& the slog file is not there in the trans/log directory

Error while running a OA framework Page Process exited with exit code 1.

Hi all,
I downloaded the Patch 4573517 from Metalink for JDEV with OA extension release 11i.I followed all the instruction of the setup init and installed the Jdev,also mytutorial pages got compiled successfully,but when i trie dto run the page
Run > Run test_fwktutorial.jsp from the main menu.
it gives me error.The error is as follows
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\D drive\OA_2008\jdevbin\jdk\bin\javaw.exe -client -classpath C:\D drive\OA_2008\jdevbin\j2ee\home\oc4j.jar;C:\D drive\OA_2008\jdevbin\jdev\lib\jdev-oc4j.jar -Xbootclasspath/p:C:\D drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip -DFND_JDBC_STMT_CACHE_SIZE=200 -DCACHENODBINIT=true -DRUN_FROM_JDEV=true -mx256m -Doracle.j2ee.dont.use.memory.archive=false -Xverify:none -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 com.evermind.server.OC4JServer -config C:\D drive\OA_2008\jdevhome\jdev\system9.0.3.5.1437\oc4j-config\server.xml
[waiting for the server to complete its initialization...]
java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
Exception in thread "main"
Process exited with exit code 1.
I am not understanding why it is going in exception.One reason which i doubthere is the line
java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
here in this line the last word is ojdbc14/jar,i think it should have been ojdbc14.jar.
Can any body please help me out on how to correct this problem.Thanks
Manish

Manish,
You should ask on the OA Framework Forum.
john

Installation of Photoshop update 13.1.2 for creative cloud fails with error code U44M1P7 I need help

I need help installing update 13.1.2 for Photoshop creative cloud, installation fails with error code: U44M1P7. Could someone please help?

Sorry to bother you.
I could find the answer after searching previous posts about this language problem.
Had to change my language in AAM profile and then download PS CS6 again ( english version ).
Then open the actual Photoshop and in preferences > interface you can besides the Dutch also option for English.
restart application and Voila.
Greetz, Jeroen

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

What is wrong with this code? on(release) gotoAndPlay("2")'{'

Please could someone tell me what is wrong with this code - on(release)
gotoAndPlay("2")'{'
this is the error that comes up and i have tried changing it but it is not working
**Error** Scene=Scene 1, layer=Layer 2, frame=1:Line 2: '{' expected
     gotoAndPlay("2")'{'
Total ActionScript Errors: 1 Reported Errors: 1
Thanks

If you have a frame labelled "2" then it should be:
on (release) {
    this._parent.gotoAndPlay("2");
or other wise just the following to go to frame 2:
on (release) {
     this._parent.gotoAndPlay(2);
You just had a missing curly bracket...

TO is unble to confirm with T-code LM02

Similar Messages

Maybe you are looking for