Vm Ware Inventory
Hi ,
I am using VMware (ESX), I installed 3 sap instances on that .unfortunate i removed(REMOVE FROM INVENTORY) one instance from VMware insted of DELETE FROM DISK so my space has freezed their how can i relocate that space .can any one have any idea.please do need full.
Thanks in Advance.
manikanta
Hi Nagammani,
As per as my knowledge "Storage VMotion" can be used to realocate freezed space.
Please look for Storage Vmotion
THanks
Debdeep
Similar Messages
-
Automatic creation software metering rules
hi
I have installed SCCM 2012 r2 with two servers .A site server and a database server .I enabled software metering on client settings and software and hard ware inventory .But I ve got a problem that sccm doesn't create software metering rules automatically
.I had already enabled Automatic create software metering rule on SMW properties . But no luck yet.
when I create a rule manually It works fine but Its not working automatically .you have configured 2% of computers must use the disabled programs to activate automatically (Specify
the percentage of computers in the hierarchy that must use a program before a software metering rule is automatically created) .so pls check if any of the computers are using the disabled programs or not.Login to test computer and use the disabled
program and then check the status.
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr
I have more than 500 clients with enabled software metering .Dont you think it is enough to create rules automatically .? -
WM Inventory Document Cleared with Item not counted
Hi.
I have a strange situation. There is a WM Inventory Document with status Cleared, but there is a Item with status Not Counted.
The differences ware already cleared via LI21/LI20 but due the Not Counted Item, the quant is still blocked by inventory.
Do you have some idea how can I count/clear this item and release the quant?
Thanks in advance.M7706 is a hard coded error message, you cannot control it via message attributes.
What you can do is to do a re-count via transaction MI11 with reference to this inventory document. In this case you will be able to add new items, however, you have to enter the counted amounts for the existing items again.
But in my opoinion it's easier to create a new PID as suggested by Jurgen. -
Yesterday, while playing Mafia Wars, I kept getting a bar notification that "The game can not load completely because you are missing a plugin? When I clicked on the box I got an 1/2" popup, which probably contains the information I need but it is too small to find out what it is. You can not maximize it. The is nothing visible to click on. Flash and Java are all up to date, as well as all other plugins. No plugins are disabled. How can I find what I am missing?
Try a program such as Disk Inventory X or OmniDiskSweeper.
(50778) -
Reusing login credentials with multiple wars
I have 2 web applications (war files) that are deployed to a single managed server. Both web applications use the weblogic security realm for authentication (configured via Security Realm -> Providers) with the same provider. This means that both applications have the same set of users.
The first application implements a simple web service (using JAX-WS) that provides 3 or 4 functions.
The second application is a UI that provides inventory operations (saved to a database) and additionally calls functions from the first web service application.
I would like the following to happen:
1 - User logs into the UI application
2 - User performs an action that calls the web service application
3 - The UI application uses the login credentials from step 1 to login to the web service application
4 - The web service application executes the function with the user credentials from step 1
The reason I would like this is that the web service application has an audit trail of who called the function.
I have a work around but it is not acceptable, which is to configure a username/password in the UI. The issue is that the web service function is always called with the configured user, regardless of who logs in from step 1.
Anyone have any ideas on how to deal with this problem?
Does SSO help in this case?
Is there a way to reuse the session?While logged in as User B, open Keychain Access. Find the password entry for connecting to the mini and delete it.
Then, try to log in again. User B likely used User A's login info at some point, maybe testing, to connect to the mini, so those credentials were saved in the keychain. -
In Physical Inventory Check_Which movement type used for stock difference.
In Case of Physical Inventory we are getting the stock differences after count results, Help me in doing the transaction thru which the stock is adjusted and which Movement types are used for the difference posting, What all documents are created in the process.
The system has Warehouse Management in place, so please answer in reference to WM.
How the Bin is identified in that case if there is stock addition.
Thanks in AdvanceHI,
Check for your ware house physical inventory process in spro whether it is done through continuous inventory process or Through annual inventory process.
SproLogistics execution-WM>Activities->Physical inventory--> Define types per storage type
PZ-Continous inv
ST-Annual
Regards,
velu -
SAP Inventory management interface with Third party Warehouse System
Hi Experts,
Need your input for designing the SAP solution with existing Third party warehouse system ( Exacta ):-
SAP ERP will be implemented for all locations of Client ( SAP MM, FI, PS , HR etc ).The Client has 10 distribution centres which are on Exacta Warehouse systems and will be linked with SAP Inventory management system.
The way it will work - Goods receipt will always happen in SAP for all locations and then interface needs to Trigger subsequent Putaway activities at Exacta Ware house ( third party warehouse system) for those 10 locations.
Goods Issue for these locations will happen from Exacta and then update will be posted in SAP via interface.
All locations will be created as Plant /Storage locations in SAP.
Need your inputs what special configurations need to happen in SAP for those locations so that goods receipt in SAP can trigger putaway activities in Exacta system .
Do we need to do configuration for decentralised Warehouse in SAP for handling this?
Pl. give your inputs based on your past experience where you handled such scenarios via interface with SAP Inventory management and legacy warehouse systems.
Thanks for quick response on this.
Regards,
KrishKrish
This is a std business process where clients have used their existing warehousing systems but implemented SAP forother functions such as Order entry, inventory mgmt and procurement, financials.
The typical interface that needs to happen is
1. Sales order ( and or delivery)
2. Invetory needs to be passed to the WH. Typically people send it when SAP GR takes place.
3. When WH system does picking, it sends signal to SAP which then does PGI for the sales order delivery and that takes the stock out of the system.
Material master has to be transferred or mapped between two systems. Also, other elements need to be mapped between two systems.
The way I have seen this happening is :
you have an output on the SAP GR process. That creates an idoc to the WH system. Based on the capabilities of the WH system, it then does appropriate actions in the system.
Many times, middlewares are used to translate/ map the data between SAP and the WH systems.
So system wise, there is ALE setup that needs to take place for IDOC creations.
Configuration and coding is required for the output type and the program behind it. There are several std FUnction Modules that can be used for this.
Hope this helps.
Mankai -
SAP inventory management interface with third party warehouse
Hi Experts,
Need your input for designing the SAP solution with existing Third party warehouse system ( Exacta ):-
SAP ERP will be implemented for all locations of Client ( SAP MM, FI, PS , HR etc ).The Client has 10 distribution centres which are on Exacta Warehouse systems and will be linked with SAP Inventory management system.
The way it will work - Goods receipt will always happen in SAP for all locations and then interface needs to Trigger subsequent Putaway activities at Exacta Ware house ( third party warehouse system) for those 10 locations.
Goods Issue for these locations will happen from Exacta and then update will be posted in SAP via interface.
All locations will be created as Plant /Storage locations in SAP.
Need your inputs what special configurations need to happen in SAP for those locations so that goods receipt in SAP can trigger putaway activities in Exacta system .
Do we need to do configuration for decentralised Warehouse in SAP for handling this?
Pl. give your inputs based on your past experience where you handled such scenarios via interface with SAP Inventory management and legacy warehouse systems.
Thanks for quick response on this.
Regards,
Krish
Edited by: krishnendu Bhowmik on Nov 24, 2009 4:22 PMHi experts,
Any inputs on this .
Thanks again,
Krish -
How to do Physical inventory process in Warehouse
Hi Guys
What is the procedure for Physical inventory process in Ware house
Kindly provide step by step procedueHi
Please go with following transaction
MI01>Create physical inventory document>Enter Document Date>Planned count date>Plant Code>Storage Location>Click on Enter button>you will get the separate screen>Enter material code>and click on SAVE button (Ctrl+S)>you will get Physical inventory document number. (MI02-Use for delete)
(After getting Physical inventory document number you go with MIO4)
MI04>click on enter button>you will get "Enter inventory count screen>Enter Phys. inventory doc.no>Fiscal year>Count date>click on enter button>you will get separate screen>Enter physical qty>and click on save button ((Ctrl+S)>you will get massage from the SAPu201D Count entered for phys. inv. doc. 100000112"
(After completed above transaction you please go with MI07)
MI07>you will get Post inv.differences: initial screen>Enter Phys. inventory doc.> Fiscal year> Posting date>click on enter button>you will get separate screen with deference qty>click save button (Ctrl+S)> you will get document number generated from the system (Diffs in phys. inv. doc. 100000112 posted with m. doc. 4900001246)
Physical Inventory:
Physical Inventory is a business process in which physical stock is matched with book (system) stock. It is legal requirement to carry out physical inventory at least once in a year.
Physical inventory can be carried out both for a companyu2019s own stock (Unrestricted, Quality, Blocked Stock) and for special stocks (Customer Consignment stock, Vendor consignment stock from vendor, Returnable packaging). This inventory is carried out saperately for both type of stocks.
Physical Inventory Processes:
Several inventory processes available for physical inventory which includes as follow:
1. Periodic Physical Inventory
o All stocks of the company are physically counted on the balance sheet key date
o Every material must be counted
o Entire warehouse must be blocked for material movements during count.
2. Continuous Physical Inventory
o Stocks are counted continuously during the entire fiscal year.
o It is important to ensure that every material is physically counted at least once during the year.
3. Cycle Counting
o In this method of physical inventory, inventory is counted at regular intervals within a fiscal year.
o These intervals (or cycles) depend on the cycle counting indicator set for the material in Material Master record as CC indicator in plant view data.
o With this Cycle Counting Method of Physical Inventory allows fast-moving items to be counted more frequently than slow-moving items.
4. Inventory Sampling
o Randomly selected stocks of the company are physically counted on the balance sheet key date.
o If found not much variance between the counted stock and the book book stock, it is presumed that the book inventory balances for the other stocks are correct.
Physical Inventory Process Cycle Flow
1. Creation of physical inventory document
- Physical inventory document(s) is created individually or using the batch program, click for more information
- The transaction codes for creation physical inventory are as follow
Individual Inventory documentation creation
MI01 - Individual physical inventory creation
MIS1 - Inventory Sampling document creation
MICN - Cycle count inventory document creation
Collective Inventory document creation
MI31 - Own stock without special stock
MIK1 - Vendor consignment
MIQ1 - Project stock
MIM1 - Returnable Transpiration material
MIW1 - Customer Consignment stock
MIV1 - Returnable material with customer
MIO1 - Material provided to Vendor (Subcontracting material)
2. Print physical inventory document
- Physical Inventory document can be printed based on the physical inventory document status and or item status
- Transaction code MI21 is used to print the inventory document where print default value can be populated
3. Count the physical stock
- Based on the inventory document printout, the warehouse person will check the stock of material physically and note that on print out. This is completely physical process.
4. Enter count in system
- On completion of physical count, the count result is needs to be entered in the system. This can be with reference (using Tcode MI04) or without reference (using Tcode MI04) to the physical inventory document.
- If count quantity for that material is ZERO then select ZC (zero count) column instead of putting 0 in qty field. If 0 is used for zero count then systm will consider that as "not counted"
5. Analyze difference
- Once count is posted in the system, difference analysis can be carried out using transaction MI20
- The output gives information based on the input criteria i.e. physical inventory document, plant, material etc.
- The output gives information about the book quantity, Counted quantity, difference in quantity and value.
- From this output list, you can carry out further process ie initiate recount, change count quantity, post difference
6. Initiate recount and follow the steps 3,4,5
- If found unacceptable difference, recount is initiated using directly from difference analysis list (transaction code MI20) or using transaction code MI11.
- New inventory document will be created for selected items or for entire document
- The original document items will be deactivated once recount is initiated so original document will not be available for further process.
- On initiating recount, you need to process same as for new count document.
7. Post the difference
- Several options are available for posting difference
- Post difference after count is posted using transaction code MI07
- Posting the count and inventory differences using transaction code MI08, here you have created physical inventory but not counted so with this you can count and post difference in sinle step.
- Entering the count without a document reference using trasnaction code MI10, with this you can create inventory document, enter the count and post difference in single step.
some more points for posting difference
- Posting period must be open to post inventory difference.
- The fiscal year is set by specifying a planned count date when creating a physical inventory document.
- Tolerence to crear difference per user group can be set in customization.
- The system will generate material document for the difference qty and post the value to appropriate account (for valuated stock)
- The movement type in material document will be 701 or 702 based on gain or loss of material.
Serial Numbers in Physical Inventory
If material is managed with serial number then it is possible to carry out physical inventory for material with serial number. There are some pre-requisite before you carry out physical inventory for serialized materials.
- Serial number profile must be maintained in the material master.
- the serialization procedure MMSL (maintaining goods receipt and goods issue documents) has to be assigned to serial number profile.
- The stock check indicator in the serial number profile should be configured.
- Maintain basic settings for the serial numbers in customization for Serial Number Profile.
- Configure serial number management for physical inventory in the Settings for Physical Inventory step in Customizing for Inventory Management.
Blocked Stock Returns are the stock which is return stock from Customer or the stock which can be return back to vendor. To restrict the usage of this stock mostly business do transfer posting for this mateial as BLOCKED stock
Goto SPRO -> Sales and Distribution -> Billing -> goto Copy Control -> use Copy control Between billing doc to sales doc.
select the line which refers to ur billing doc and Return Sales doc.
Goto Item level and please check the Check box saying Update Doc Flow .
This check box will keep track of Refernce qty between Billing Doc and Return Sales Doc.
Rgds,
Rajesh -
Things to be done before Physical Inventory Process
Hi
Just before i do Physical Inventory process, what are the pre-requisites should I consider.
For example, Sales order stock already alloted. And I am posting a count value less than that. I usaully get an error.
Kindly list me such things which i should clear in the SAP system before i do PI process.
Regards
Maruthi Ramhi,
before doing physical inventory we need to check the following
1. check the ware house stock thru MB53.MB5B
2. confirm whether physical inventory for the entire plant or a particular sto loc
3. decide which process you are going to use for PI count ( either manual/batch /cycle count)
4. if the process is cycle count check whether all the materials having CC indicator
5. decide whether we need to block or freeze the posting
6. decide which you are going to stop the transaction if the physical inv is blocked.
hope this will be useful
Regards
Sridharan -
Hello friends,
I have client interview on this "WARE HOUSE MANAGEMENT AND LEAN WARE HOUSE MANAGEMENT" . So please help me out by sending good material. Really waiting for good support.
Thanks,
Rams.from here questions are also asked in the certification exams, so here's a point-wise rant:-
If you have a warehouse with random storage, you need to use the WM System with full functionality. Since a material can be stored in different storage bins or even several storage bins at the same time, precise inventory management at the level of the storage bin is required.
 Lean WM does not have inventory management at the level of the storage bin and is therefore more suitable for fixed bin warehouses. In a fixed bin storage area, the material is always in the same storage bin.
 To print the storage bin in the picking document, you must maintain the respective data in the material master in the view "Storage 1". Maintenance of further warehouse data and the Warehouse Management views is not required.
 Some of the WM functions not included in Lean WM are listed below:
 Storage sections
 Reserve storage bins
 Strategies for putaway and picking
 Replenishment
 Inventory at storage-bin level
This considerably reduces implementation effort.
 For Lean WM you need at least one warehouse number and at least one storage type from which picking takes place and one storage type in which goods are stored (for example, picking storage type as source storage type, shipping zone as destination storage type).
 In the picking storage area, you can have storage bins grouped together from the stock removal viewpoint (for example, to distribute the workload evenly). Picking areas can be defined for each warehouse number and storage type.
 In addition to the picking area, there are other organizational units in the warehouse. These are the staging areas and the doors. They are defined in the outbound delivery or determined by the system and they can also be printed out on the picking documents.
 You can activate Lean WM in Customizing at the warehouse number level.
 You assign a warehouse number to a combination of plant and storage type. In this way, the organizational units in the warehouse are linked up to MM Inventory Management. Also, through this assignment, a status for WM activities is assigned to the respective items in the outbound delivery. -
War that works on mozilla/netscape not ie
I have a jsp/war app that was written for me to operate with iplanet6. When I moved it to appserver7 it will only respond to netscape/mozilla correctly and I get session timeout, login failed using IE. It behaves the same if I access accross the LAN or using the local machine.
The server is W2K with current patches. The db for the app is Sybase ASA 8 with patches. The db and appserver are running on the same machine.
Server log and access file below showing failed login then sucessful login.
server log
[11/Dec/2003:11:12:29] INFO ( 2860): CORE1116: Sun ONE Application Server 7.0.0_01
[11/Dec/2003:11:12:29] FINE ( 2860): Collecting statistics for up to 1 processes with 128 threads, 200 listen sockets, and 1000 virtual servers
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP5169: User authentication cache entries expire in 120 seconds.
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP5170: User authentication cache holds 200 users
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP5171: Up to 4 groups are cached for each cached user.
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP4207: file cache module initialized (API versions 1 through 1)
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP4302: file cache has been initialized
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP3063: KeepAliveTimeout is 30 seconds (default value)
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP3067: PostThreadsEarly set to off
[11/Dec/2003:11:12:29] FINE ( 2860): HTTP3066: MaxKeepAliveConnections set to 256
[11/Dec/2003:11:12:29] FINE ( 2860): Installed configuration 1
[11/Dec/2003:11:12:29] FINE ( 2860): jvm stickyAttach: 1
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -DJAVA_HOME=C:/j2sdk1.4.2
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.installRoot=C:/Sun/AppServer7
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.instanceRoot=C:\Sun\AppServer7\domains\domain1
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Duser.language=en
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Duser.country=US
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: exit
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: vfprintf
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Djava.security.policy=C:/Sun/AppServer7/domains/domain1/server1/config/server.policy
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Djava.security.auth.login.config=C:/Sun/AppServer7/domains/domain1/server1/config/login.conf
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.jdo.api.persistence.model.multipleClassLoaders=reload
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Djava.util.logging.manager=com.iplanet.ias.server.logging.ServerLogManager
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.configRoot=C:/Sun/AppServer7\config
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.imqLib=C:\Sun\AppServer7\imq\lib
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.imqBin=C:\Sun\AppServer7\imq\bin
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dcom.sun.aas.webServicesLib=C:\Sun\AppServer7\share\lib
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Dsun.rmi.dgc.server.gcInterval=3600000
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Xms128m
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Xmx256m
[11/Dec/2003:11:12:29] FINE ( 2860): jvm option: -Djava.class.path=C:/Sun/AppServer7/lib/appserv-rt.jar;C:/j2sdk1.4.2/lib/tools.jar;C:/Sun/AppServer7/lib/appserv-ext.jar;C:/Sun/AppServer7/lib/appserv-cmp.jar;C:\Sun\AppServer7\share\lib/mail.jar;C:/Sun/AppServer7/lib/appserv-ideplugin.jar;C:\Sun\AppServer7\imq\lib/imq.jar;C:\Sun\AppServer7\imq\lib/jaxm-api.jar;C:\Sun\AppServer7\imq\lib/imqadmin.jar;C:\Sun\AppServer7\imq\lib/imqutil.jar;C:/Sun/AppServer7/lib/appserv-admin.jar;C:\Sun\AppServer7\share\lib/jaxrpc-impl.jar;C:\Sun\AppServer7\share\lib/jaxrpc-api.jar;C:\Sun\AppServer7\share\lib/jaxr-impl.jar;C:\Sun\AppServer7\share\lib/jaxr-api.jar;C:\Sun\AppServer7\share\lib/activation.jar;C:\Sun\AppServer7\share\lib/saaj-api.jar;C:\Sun\AppServer7\share\lib/saaj-impl.jar;C:\Sun\AppServer7\share\lib/commons-logging.jar;C:\Sun\AppServer7\imq\lib/fscontext.jar;C:\Sun\AppServer7\imq\lib/providerutil.jar;C:/Sun/AppServer7/lib/appserv-jstl.jar;C:/Sun/AppServer7/pointbase/client_tools/lib/pbclient42RE.jar;
[11/Dec/2003:11:12:31] FINE ( 2860): reinitializeLogger: javax.enterprise.system.core com.sun.logging.enterprise.system.core.LogStrings FINE
[11/Dec/2003:11:12:31] FINE ( 2860): reinitializeLogger: null FINE
[11/Dec/2003:11:12:31] FINE ( 2860): reinitializeLogger: global null FINE
[11/Dec/2003:11:12:31] FINE ( 2860): reinitializeLogger: javax.enterprise.system.util com.sun.logging.enterprise.system.util.LogStrings FINE
[11/Dec/2003:11:12:31] FINE ( 2860): reinitializeLogger: javax.enterprise.system.core.config com.sun.logging.enterprise.system.core.config.LogStrings FINE
[11/Dec/2003:11:12:31] INFO ( 2860): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2] from [Sun Microsystems Inc.]
[11/Dec/2003:11:12:31] FINE ( 2860): initializeServerLogger: javax.enterprise.system.tools.verifier com.sun.logging.enterprise.system.tools.verifier.LogStrings FINE
[11/Dec/2003:11:12:31] FINE ( 2860): Setting xpath for the whole tree
[11/Dec/2003:11:12:31] FINE ( 2860): Finished setting xpath for the whole tree
[11/Dec/2003:11:12:31] FINE ( 2860): initializeServerLogger: javax.enterprise.system.core.classloading com.sun.logging.enterprise.system.core.classloading.LogStrings FINE
[11/Dec/2003:11:12:31] FINE ( 2860): Adding jar to class path:file:/C:/Sun/AppServer7/domains/domain1/server1/lib/jconn2.jar
[11/Dec/2003:11:12:32] FINE ( 2860): initializeServerLogger: javax.enterprise.resource.jms com.sun.logging.enterprise.resource.jms.LogStrings FINE
[11/Dec/2003:11:12:32] FINE ( 2860): initializeServerLogger: com.sun.jdo.persistencemanager com.sun.jdo.spi.persistence.support.sqlstore.Bundle FINE
[11/Dec/2003:11:12:32] FINE ( 2860): initializeServerLogger: javax.enterprise.system.tools.admin com.sun.logging.enterprise.system.tools.admin.LogStrings FINE
[11/Dec/2003:11:12:33] FINE ( 2860): Starting JMS broker : imq-home=C:\Sun\AppServer7\imq\bin, initTimeout=30000, stargArgs=null, instanceName=domain1_server1
[11/Dec/2003:11:12:45] INFO ( 2860): JMS5023: JMS service successfully started. Instance Name = domain1_server1, Home = [C:\Sun\AppServer7\imq\bin].
[11/Dec/2003:11:12:45] FINE ( 2860): Setting xpath for the whole tree
[11/Dec/2003:11:12:45] FINE ( 2860): Finished setting xpath for the whole tree
[11/Dec/2003:11:12:45] FINE ( 2860): initializeServerLogger: javax.enterprise.system.core.security com.sun.logging.enterprise.system.core.security.LogStrings FINE
[11/Dec/2003:11:12:46] FINE ( 2860): initializeServerLogger: javax.enterprise.resource.corba com.sun.logging.enterprise.resource.corba.LogStrings FINE
[11/Dec/2003:11:12:46] FINE ( 2860): initializeServerLogger: javax.enterprise.system.core.transaction com.sun.logging.enterprise.system.core.transaction.LogStrings FINE
[11/Dec/2003:11:12:46] FINE ( 2860): J2EE server listen port: 3700
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 2.23.130.1.1.1
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 67 81 02 01 01 01
[11/Dec/2003:11:12:47] FINE ( 2860): GSSUP_MECH_OID: 06 06 67 81 02 01 01 01
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 1.3.6.1.5.6.4
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 2b 06 01 05 06 04
[11/Dec/2003:11:12:47] FINE ( 2860): GSS_NT_EXPORT_NAME_OID: 06 06 2b 06 01 05 06 04
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 2.23.130.1.2.1
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 67 81 02 01 02 01
[11/Dec/2003:11:12:47] FINE ( 2860): GSS_NT_SCOPED_USERNAME_OID: 06 06 67 81 02 01 02 01
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 2.23.130.1.1.1
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 67 81 02 01 01 01
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 2.23.130.1.1.1
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 67 81 02 01 01 01
[11/Dec/2003:11:12:47] FINE ( 2860): Returning OID in DER format
[11/Dec/2003:11:12:47] FINE ( 2860): OID = 2.23.130.1.1.1
[11/Dec/2003:11:12:47] FINE ( 2860): DER OID: 06 06 67 81 02 01 01 01
[11/Dec/2003:11:12:47] FINE ( 2860): Naming service started:3700
[11/Dec/2003:11:12:47] FINE ( 2860): initializeServerLogger: javax.enterprise.system.core.naming com.sun.logging.enterprise.system.core.naming.LogStrings FINE
[11/Dec/2003:11:12:47] FINE ( 2860): initializeServerLogger: sun.rmi.loader null FINE
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:47] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:47] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:47] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:47] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:47] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:47] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:47] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:47] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:47] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:47] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:47] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:47] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:47] FINE ( 2860): Properties set are :{ [ com.sun.CORBA.threadpool.maxthreads->200 ] [ com.sun.CORBA.ORBServerHost->192.168.0.2 ] [ com.sun.enterprise.J2EEServerId->100 ] [ com.sun.jts.heuristicDirection->rollback ] [ com.sun.jts.persistentServerId->100 ] [ com.sun.CORBA.connection.ORBHighWaterMark->1024 ] [ com.sun.CORBA.giop.ORBBufferSize->1024 ] [ com.sun.CORBA.ORBAllowLocalOptimization->true ] [ org.omg.PortableInterceptor.ORBInitializerClass.com.sun.enterprise.iiop.J2EEInitializer-> ] [ com.sun.CORBA.threadpool.minthreads->10 ] [ com.sun.CORBA.orb.AddrAnyAddress->0.0.0.0 ] [ com.sun.CORBA.giop.ORBFragmentSize->1024 ] [ com.sun.jts.keypointCount->2048 ] [ org.omg.CORBA.ORBSingletonClass->com.sun.corba.ee.internal.corba.ORBSingleton ] [ org.omg.CORBA.ORBClass->com.sun.enterprise.iiop.POAEJBORB ] [ org.omg.PortableInterceptor.ORBInitializerClass.com.sun.enterprise.iiop.IORAddrAnyInitializer-> ] [ com.sun.CORBA.ORBServerPort->3700 ] [ com.sun.jts.logDirectory->C:/Sun/AppServer7/domains/domain1/server1/logs\tx ] [ com.sun.CORBA.threadpool.timeout->300000 ] }
[11/Dec/2003:11:12:47] INFO ( 2860): JTS5014: Recoverable JTS instance, serverId = [100]
[11/Dec/2003:11:12:47] FINE ( 2860): serverName = jason,P100; isRecoverable = true
[11/Dec/2003:11:12:47] FINE ( 2860): Property :com.sun.jts.timeoutInterval has the value : null
[11/Dec/2003:11:12:47] FINE ( 2860): Before starting ResyncThread
[11/Dec/2003:11:12:47] FINE ( 2860): Before invoking RecoveryManager.recover()
[11/Dec/2003:11:12:47] FINE ( 2860): Initializing configured realms.
[11/Dec/2003:11:12:47] FINE ( 2860): Property :com.sun.jts.keypointCount has the value : 2048
[11/Dec/2003:11:12:47] FINE ( 2860): Using directory = C:/Sun/AppServer7/domains/domain1/server1/logs\tx : provided in configuration
[11/Dec/2003:11:12:48] FINE ( 2860): FileRealm : file=C:/Sun/AppServer7/domains/domain1/server1/config/keyfile
[11/Dec/2003:11:12:48] FINE ( 2860): FileRealm : jaas-context=fileRealm
[11/Dec/2003:11:12:48] FINE ( 2860): Reading file realm: C:/Sun/AppServer7/domains/domain1/server1/config/keyfile
[11/Dec/2003:11:12:48] FINE ( 2860): Configured realm: file
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : directory=ldap://localhost:389
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : base-dn=o=isp
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : jndiCtxFactory=com.sun.jndi.ldap.LdapCtxFactory
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : jaas-context=ldapRealm
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : mode=find-bind
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : search-filter=uid=%s
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : group-base-dn=o=isp
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : group-search-filter=uniquemember=%d
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : group-target=cn
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : search-bind-dn=null
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : search-bind-password=null
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : pool-size=5
[11/Dec/2003:11:12:48] FINE ( 2860): LDAPRealm : authentication=simple
[11/Dec/2003:11:12:48] FINE ( 2860): Before invoking proceedWithXARecovery()
[11/Dec/2003:11:12:48] FINE ( 2860): Property :com.sun.jts.ManualRecovery has the value : null
[11/Dec/2003:11:12:48] FINE ( 2860): Configured realm: ldap
[11/Dec/2003:11:12:48] FINE ( 2860): Configured realm: certificate
[11/Dec/2003:11:12:48] FINE ( 2860): Default realm is set to: file
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): initializeServerLogger: javax.enterprise.resource.jta com.sun.logging.enterprise.resource.jta.LogStrings FINE
[11/Dec/2003:11:12:48] FINE ( 2860): initializeServerLogger: javax.enterprise com.sun.logging.enterprise.LogStrings FINE
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_exception
[11/Dec/2003:11:12:48] FINE ( 2860): initializeServerLogger: javax.enterprise.resource.resourceadapter com.sun.logging.enterprise.resource.resourceadapter.LogStrings FINE
[11/Dec/2003:11:12:48] FINE ( 2860): Loading Jdbc Connection Pool==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading Jdbc Resource==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading Jms Resource==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading PMF Resource==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading Custom Resource==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading External Jndi Resource==========
[11/Dec/2003:11:12:48] FINE ( 2860): Loading Mail Resource==========
[11/Dec/2003:11:12:48] INFO ( 2860): RAR5060: Install JDBC Datasources ...
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] INFO ( 2860): RAR5059: Binding [JDBC DataSource Name: Inventory, Pool Name: SybasePool]
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): In start of IASConnectionManagerImpl.initializeSecurityTable(...)
[11/Dec/2003:11:12:48] FINE ( 2860): in IASMCFFactory
[11/Dec/2003:11:12:48] FINE ( 2860): After getting IASMCFFactory.
[11/Dec/2003:11:12:48] FINE ( 2860): After getting listOfJNDIName.
[11/Dec/2003:11:12:48] FINE ( 2860): After creating securityTable.
[11/Dec/2003:11:12:48] FINE ( 2860): In end of IASConnectionManagerImpl.initializeSecurityTable(...)
[11/Dec/2003:11:12:48] FINE ( 2860): In end of IASConnectionManagerImpl constructor.
[11/Dec/2003:11:12:48] FINE ( 2860): In end of IASPoolManager constructor
[11/Dec/2003:11:12:48] INFO ( 2860): JMS5015: Install JMS resources ...
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:48] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:48] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:48] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:48] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: javax.enterprise.system.container.ejb com.sun.logging.enterprise.system.container.ejb.LogStrings FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: javax.enterprise.system.container.web com.sun.logging.enterprise.system.container.web.LogStrings FINE
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:49] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:49] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:49] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:49] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:49] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:49] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:49] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:49] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::send_request()
[11/Dec/2003:11:12:49] FINE ( 2860): Security context is null (nothing to add to service context)
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): ++++ Entered SecClientRequestInterceptor::receive_reply
[11/Dec/2003:11:12:49] FINE ( 2860): No SAS context element found in service context list
[11/Dec/2003:11:12:49] FINE ( 2860): Status to be set : 0
[11/Dec/2003:11:12:49] FINE ( 2860): Invoked receivedReply()
[11/Dec/2003:11:12:49] FINE ( 2860): J2EE server startup complete.
[11/Dec/2003:11:12:49] FINE ( 2860): Application server configuration file: C:\Sun\AppServer7\domains\domain1/server1/config/server.xml
[11/Dec/2003:11:12:49] FINE ( 2860): Application Server default locale is en_US
[11/Dec/2003:11:12:49] FINE ( 2860): Web container log level: FINE
[11/Dec/2003:11:12:49] FINE ( 2860): Successfully initialized web application environment for virtual server [server1]
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.client.ref null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.client.call null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.server.ref null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.server.call null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.transport.misc null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.transport.tcp null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.transport.tcp.proxy null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): main: localHostKnown = true, localHost = 192.168.0.2
[11/Dec/2003:11:12:49] FINE ( 2860): main: Version = 2, ep = [192.168.0.2:0,com.iplanet.ias.admin.server.core.channel.LocalRMIServerSocketFactory@baa31b,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@12a66ea]
[11/Dec/2003:11:12:49] FINE ( 2860): main: created local endpoint for socket factory com.iplanet.ias.admin.server.core.channel.LocalRMIServerSocketFactory@baa31b on port 0
[11/Dec/2003:11:12:49] FINE ( 2860): main: (port 0) create server socket
[11/Dec/2003:11:12:49] FINE ( 2860): main: default port for server socket factory com.iplanet.ias.admin.server.core.channel.LocalRMIServerSocketFactory@baa31b and client socket factory com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@12a66ea set to 4029
[11/Dec/2003:11:12:49] FINE ( 2860): RMI TCP Accept-0: listening on port 4029
[11/Dec/2003:11:12:49] FINE ( 2860): initializeServerLogger: sun.rmi.dgc null FINE
[11/Dec/2003:11:12:49] FINE ( 2860): main: Version = 2, ep = [192.168.0.2:0]
[11/Dec/2003:11:12:49] FINE ( 2860): main: created local endpoint for socket factory null on port 0
[11/Dec/2003:11:12:50] FINE ( 2860): initializeServerLogger: javax.enterprise.system.tools.deployment com.sun.logging.enterprise.system.tools.deployment.LogStrings FINE
[11/Dec/2003:11:12:50] FINE ( 2860): Default role is: ANYONE
[11/Dec/2003:11:12:50] INFO ( 2860): WEB0100: Loading web module [inventory] in virtual server [server1] at [inventory]
[11/Dec/2003:11:12:50] FINE ( 2860): WebModule[inventory]: Setting delegate to false
[11/Dec/2003:11:12:50] FINE ( 2860): WEB0100: Loading web module [default-web-module] in virtual server [server1] at []
[11/Dec/2003:11:12:50] FINE ( 2860): WebModule[]: Setting delegate to false
[11/Dec/2003:11:12:51] FINE ( 2860): WebappLoader[inventory]: Deploying class repositories to work directory C:\Sun\AppServer7\domains\domain1\server1\generated\jsp\j2ee-modules\inventory
[11/Dec/2003:11:12:51] FINE ( 2860): WebappLoader[inventory]: Deploy JAR /WEB-INF/lib/gcsoft.jar to C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\inventory_2\WEB-INF\lib\gcsoft.jar
[11/Found a solution!
Here it is in case anyone else ever comes across this issue:
var Accordion1 = new Spry.Widget.Accordion("Accordion1", { defaultPanel: <?php echo($totalRows_recordsetName - 1); ?> }); -
Inventory doc. number range
Hi,
I try to create inventory document for 203 and 204 warehouse, but I canu2019t. There is warring message (Maintain number range interval u201803u2019 for inventory documents).
With Regards,
Jaheer.Hi,
Goto IMG> MM>InvMgmnt and PhyInv>Number Assignment..
Define and Assign number assmnt..
That will solve your problem.
Edited by: Antony anburaj on May 1, 2010 2:19 PM -
Lean ware house management screen shots
Hi sd gurus,
now my client is having requirement of lean ware house mgmt ,can any one send me screen shots for configuration process
to my mail id [email protected]Hi Srini,
Please find the complete notes on Lean Ware House Management System below:
A09 Lean Warehouse Management: Configuration Guide
Purpose
The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
The Configuration Guide describes how to set up the configuration of a Building Block manually, without the support of automated configuration tools.
Preparation
1.1 Prerequisites
The following building blocks form the basis for all mySAP All-in-One Automotive, High Tech and Industrial Machinery and Components solutions. You only have to install these building blocks once.
Building Blocks Comment
Baseline Building Blocks (Layer 0)
J00 - Essential Information
J02 - Organizational Structure
J03 - Financial Accounting
J08 - Controlling
J05 - Materials Management
J04 - Sales and Distribution
Baseline Building Blocks (Layer 1)
J06 - Production Planning and Controlling
J07 Quality Management
J18 - Product Cost Controlling
J19 Batch Management
J20 - Cost Object Controlling Make-to-Order
J21 - Cost Object Controlling Make-to-Stock
J17 - Profitability Analysis
J14 - Human Capital Management
J09 - Travel Management
Industry generic Building Blocks
E04 - Supplement Settings
E05 - Master Data HT / IM&C
Configuration
1.2 Lean WM Basic Settings
1.2.1 Defining Control Parameters and Number Ranges for the Warehouse Number Defining Control Parameters for the Warehouse Number
Use
A warehouse number is an organizational unit in Logistics, which organizes the company from the perspective of Warehouse Management.
In the Warehouse Management System, you can define a variety of control parameters at warehouse number level.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define control parameters and number ranges for the warehouse number Define control parameters and number ranges for warehouse no.(double click)
Transaction Code SM30
2. Find the Field Name and input the relative value into the field.
Table V_T3002
Field name Value R/O/C Description
Whse number L01 R
Warehouse no. description Lean WM BP01 R
Weight unit KG R
Volume unit
Default UoM K R
Time unit/performance data
Lean WM active X R
Link to subsystem active
Performance data
Transfer order 01 R
Group number 01 R
1.2.2 Defining Storage Type
Use
A warehouse number is subdivided into a variety of storage types. A storage type is defined by its physical or organizational features (for example, high rack storage area, bulk storage, and goods receipt areas).
A storage type has a short description rather than an address.
Before you can implement Lean WM, you must configure the following settings:
1. Assign a (newly defined) storage location to a warehouse number.(This step is defined by step 3.12 Control Plant / Storage Location / Warehouse Number Assignment
2. You should set up at least three storage types:
 a storage type (that will be used as a source storage type) with one or several fixed storage bins
 a goods issue area (as destination storage type) for deliveries
 an interim storage area for differences
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Storage type
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3012
Data record 1:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 001
Storage type name Fixed bin storage
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 2:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 916
Storage type name Shipping area deliveries
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 3:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 999
Storage type name Differences
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 4:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 902
Storage type name IN-ZONE
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
1.2.3 Defining Doors
Use
In a WM-managed warehouse, you can define dock doors (also known as doors or gates). A door is a location where the goods either arrive in the warehouse or leave it.
You can assign different functions to a dock door, for example:
Goods receipt
Goods issue
Other transactions such as cross-docking and flow-through
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM Define Doors
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30B
Field name Value R/O/C Description
Whse no. L01 R Warehouse number
Door A01 R Door for warehouse number
Text for door Door A01 R Text for door
Staging area
Matl stag. area txt
GI indic. X R Goods issue indicator
GR ind X R Goods receipt indicator
CD ind Cross-docking indicator
FT ind Flow-through indicator
1.2.4 Defining Material Staging Areas
Use
A staging area is an interim storage area for goods that have been received from goods receipt and afterwards need to be transferred into the warehouse.
It is also an interim storage area for goods that were picked in a warehouse and are to be loaded for goods issue through loading ramps or doors.
You can assign different functions to a staging area:
Goods issue
Goods receipt
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Material Staging Area
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30C
Field name Value R/O/C Description
Whse no. L01 R
Staging area A01-01 R
Matl stag. area txt Zone 1 R
Door A01 R Door for warehouse number
Text for door Door A01 R
GI ind X R Goods issue indicator
GR ind X R Goods receipt indicator
CD ind Cross-docking indicator
FT ind Flow-through indicator
HU ind Handling unit indicator
1.2.5 Defining Picking Area
Use
A picking area is an object within a storage type that groups together storage bins for purposes of stock removal.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM Define Picking Area
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30A2
Data record 1:
Field name Value R/O/C Description
WhN L01 R Warehouse number
STy (storage type) 001 R
PAr (Picking area) 001 R
Picking area name Picking area 1 R
Data record 2:
Field name Value R/O/C Description
WhN L01 R Warehouse number
STy (storage type) 001 R
PAr (Picking area) 002 R
Picking area name Picking area 2 R
1.2.6 Defining Transfer Type
Use
In Lean WM, the transfer type "A" (stock removal) is required for movement type control.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Transfer Type
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T333A2
Field name Value R/O/C Description
WhN L01 R Warehouse number
Transfer type A R
Text f. shipment type Pick R
1.2.7 Defining Movement Types
Use
The SAP R/3 System uses movement type to process movements in Inventory Management (for example, goods receipt for a purchase order or goods issue to a cost center). When the system recognizes a movement as being relevant for Warehouse Management, it assigns this movement to a WM movement type by means of a table.
The movement type for the Warehouse Management System provides the information required for stock removals or picking:
 Interim storage bin
 Fixed bin coordinate
 Control indicator for processing, confirming, and printing transfer orders
 Confirmation info
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Movement Type
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3332
Data record 1:
Field name Value R/O/C Description
Warehouse number L01 R
Warehouse no. description Lean WM R
Movement type 255 R
Movement type description Goods Issue general R
Src 001 R
Src Stor. Bin
Dest 916 R
Dest Stor. Bin
Transfer type A R
Text for transfer type TRATX Pick R
TO creation screen 2 R
Scr. TO confirmation 2 R
Manual TO creation not allowed
Transfer priority
Print code
TO item can be confirmed immed.
Propose confirmation
Data record 2:
Field name Value R/O/C Description
Warehouse number L01 R
Warehouse no. description Lean WM R
Movement type 601 R
Movement type description Picking by delivery note R
Src 001 R
Src Stor. bin
Dest 916 R
Dest Stor. bin
Transfer type A R
Text for transfer type TRATX Pick R
TO creation screen 2 R
Scr. TO confirmation 2 R
Manual TO creation not allowed X R
Transfer priority
Print code 02 R
TO item can be confirmed immed. X R
Propose confirmation
1.2.8 Defining Difference Indicator
Use
Using the difference indicator, you can classify your differences. This indicator is used in Lean WM for evaluation purposes only.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Difference Indicator
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3362
Field name Value R/O/C Description
WhN L01 R Warehouse number
DiffInd (difference indicator) X R
Description of difference indicator Stock difference R
Stor.ty.differences 999 R
Diff.bin
TO X R
Source bin
1.2.9 Control Plant / Storage Location / Warehouse Number Assignment
1.2.9.1 Assigning Warehouse No. to Plant-Storage Locations
Use
By doing so, system can recognize which storage locations in Materials Management are controlled by the Warehouse Management system (LE-WM); you must assign the plants and the storage location to the warehouse number.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMGEnterprise Structure Assignment  Logistic Execution  Assign warehouse No. To plant/storage Location
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T320
Field name Value R/O/C Description
Plant BP01 R
SLoc 0005 R
WhN L01 R
1.2.9.2 Control Plant / Storage Location / Warehouse Number Assignment
Use
You can control for each combination of plant, storage location, and warehouse number whether Lean WM or standard management of bin inventory is to be selected.
If you are using Lean WM, you can also specify a picking storage type that is used for creating transfer orders.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Control Plant / Storage Location / Warehouse Number Assignment
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3202
Field name Value R/O/C Description
Plnt BP01 R
Stor. loc. 0005 R
WhNo (Whse number) L01 R
Degree of activation Warehouse Mgmt 1 R
Stor.type for picking in Lean WM 001 R
1.2.10
1.2.11 Assigning Picking Location
Use
Assign the picking locations to the combinations of shipping point and storage condition for every plant.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Determine Picking Location  Assign Picking Location
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_TVKOL
Field name Value Description
ShPt BP01 Plant
Plnt BP01 Shipping point/receiving pt
SC K1 Storage conditions
SLoc 0005 Storage location
1.3 Print Control for Warehouse
Use
Print control defines the following:
Which slips are to be printed for the movements (that is, for the transfer orders) within the Warehouse Management System
How these slips are to be printed (that is, which forms are to be used, how many copies are to be printed)
On which printer a slip is to be printed automatically
And print control manages the print operations of the warehouse. This flexibility involves a certain degree of complexity with regard to the parameterization.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define Print control
Transaction Code OMLV
2. Choose the following button and check the contents
(Here only the contents of the warehouse no. L01 are listed):
2.1 Spool code
Data Record 1
Field name Value R/O/C Description
WhN L01 R Warehouse number
Spool 01 R Spool request name
Copies 1 R Number of copies
Title LVS1 R Spool control data
Print_immed. X R Print immediately
Delete_after_print X R Release after output
NewSplReq__ New spool request
Data Record 2
Field name Value R/O/C Description
WhN L01 R Warehouse number
Spool 02 R Spool request name
Copies 1 R Number of copies
Title LVS2 R Spool control data
Print_immed. Print immediately
Delete_after_print X R Release after output
NewSplReq__ New spool request
2.2 sort profile/collective process
Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7 Rec8 Rec9
WhNo_(Whse_number) L01 L01 L01 L01 L01 L01 L01 L01 L01
Sort_profile 1 2 3 4 5 6 7 8 9
1st_sort_criterion SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI
Sort_descending_order (1st_sort_criter.)
Control_break_1st_sort_criterion
2nd_sort_criterion LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI
Sortdescending_order (2nd_sort_crit.)
Control_break_2nd_sort_criterion X
3rd_sort_criterion REFNR REFNR REFNR REFNR FORMI FORMI FORMI FORMI REFNR
Sortdescending_order (3rd_sort_crit.)
Control_break_3rd_sort_criterion X X X X
4th_sort_criterion FORMI FORMI FORMI FORMI LGNUM LGNUM LGNUM LGNUM FORMI
Sortdescending_order (4th_sort_crit.)
Control_break_4th_sort_criterion X X X X
5th_sort_criterion LGNUM LGNUM LGNUM LGNUM VLTYP VLTYP VLTYP VLTYP LGNUM
Sortdescending_order (5th_sort_crit.)
Control_break_5th_sort_criterion
6th_sort_criterion VLTYP NLTYP VLTYP TANUM VLPLA NLPLA WERKS TAPOS NLTYP
Sortdescending_order (6th_sort_crit.)
Control_break_6th_sort_criterion X X X X
7th_sort_criterion VLPLA NLPLA WERKS TAPOS
TANUM TANUM LGORT KOBER
Sortdescending_order_ (7th_sort_crit.)
Control_break_7th_sort_criterion X
8th_sort_criterion TANUM TANUM LGORT TAPOS TAPOS MATNR VLPLA
Sortdescending_order (8th_sort_crit.)
Control_break_8th_sort_criterion
9th_sort_criterion TAPOS TAPOS MATNR CHARG TANUM
Sortdescending_order (9th_sort_crit.)
Control_break_9th_sort_criterion
10th_sort_criterion CHARG BESTQ
TAPOS
Sortdescending_order_ (10th_sort_crit.)
Control_break_10th_sort_criterion
11th_sort_criterion BESTQ SOBKZ
Sortdescending_order_ (11th_sort_crit.)
Control_break_11th_sort_criterion
12th_sort_criterion SOBKZ LSONR
Sortdescending_order_ (12th_sort_crit.)
Control_break_12th_sort_criterion
13th_sort_criterion LSONR VLTYP
Sortdescending_order_ (13th_sort_crit.)
Control_break_13th_sort_criterion
14th_sort_criterion VLTYP
Sortdescending_order_ (14th_sort_crit.)
Control_break_14th_sort_criterion
15th_sort_criterion
Sortdescending_order_ (15th_sort_crit.)
Control_break_15th_sort_criterion
2.3 print code
Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7
WNo___(Warehouse_number) L01 L01 L01 L01 L01 L01 L01
PrCd__(Print_code) 01 02 03 11 12 21 22
Print_code_description
Find_shipping_data____
Determine_production_data_
Form_ LVSTAEINZEL LVSTALISTE LVSTOSOLO LVSTAEINZEL LVSTALISTE LVSKOMMIL1
LVSKOMMIL2
PTm_(Time_of_printing)________
Sort_profile 1 1 1 4 1 1
Combined_print x x x x
Spool_data 02 02 01 02 02 02 02
Label_form LVSLABELS
Label_spool_code 01
Quantity_of_labels_(Indicator) 2
2.4 assign printer to storage type (LP01 to 001 only)
Field name Rec1 Rec2 Rec3
WhNo_(Whse_number) L01 L01 L01
STy__(storage_type) 001 916 999
Storage_type_description Fixed bin storage Shipping area deliveries Differences
Printer
2.5 assign print code to movement type
Field name Rec1 Rec2 Rec3
WhNo_(Whse_number) L01 L01 L01
MvT__(WM_movement_type) 101 255 601
Movement_type_description Goods receipt for pur.or.
Picking by delivery note
PrCd__(Print_code) 01 02
2.6 assign print report to warehouse No.
Field name Rec1
WhNo_(Whse_number) L01
Warehouse_number_descrip. Lean WM Plant BP01
Print_report RLVSDR40
2.7 print control multi-processing
Field name Rec1
WhN L01
Ref.ty. L
Status 2
Print_prog. RLKOMM40
PrCd 21
Printer LP01
1.4 Manual Activity
1.4.1 Maintaining Number Range Intervals for Transfer Order
Use
Maintain number range intervals for transfer order
Procedure
In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM  Define control parameters and number ranges for the warehouse number  Maintain number range intervals for transfer orders (double click)
Transaction Code LN02
Check if the internal number range 01 (0000000001-1000000000) has been defined
Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
1.4.2 Maintaining Number Range Intervals for Reference Numbers
Use
Reference number range has the following meanings:
This number identifies a number range to be used for the assignment of sequential numbers for WM reference numbers. Reference numbers are used to create or print a group of transfer orders at one time.
A sequential number generated by the system for the purpose of multiple processing of transfer requirements and delivery notes.
The reference number can also be used to print the resulting transfer orders at a later time.
Procedure
In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
Access the activity using one of the following navigation options:
IMG Menu IMG  Logistic Execution  Shipping  Picking  Lean WM Define control parameters and number ranges for the warehouse number  Maintain number range intervals for Reference Numbers( double click)
Transaction Code LN06
Check if the internal number range 01 (5000000000 - 5999999999) has been defined
Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
For Inventory Adjustment : Which Idoc type to be used and why?
Hi Gurus,
For Goods Movement in one of the MM-Purch Implementation I used the Idoc type : MBGMCR03
at that time inventaory was not playing a big role.
But for now for doing inventory adjustment (Inventory has importance now) which Idoc type to be followed:
Can I use same Idoc type : MBGMCR03
Or Shd I go for Idoc type : WMMBID02
In some threads I read if MM you shd. go for MBGMCR03 and for IM : WMMBID02.
But why I dont know the answer...
Please give me your views on this.
Thanks
AmreshMBGMCR03 is basically the BDBG idoc type and uses BAPI_GOODSMVT_CREATE to post the goods movement... You can check the documentation for the FM /BAPI to determine what kind of goods movement is possible. You can look at T158G table to find the t-codes supported. If you can post your inventory adjustment using the BAPI, you can use MBGMCR03, as long as middle ware can support that format...
As far as the WMMBID02, It uses the IDOC FM (which in turn also uses the MB_CREATE_GOODS_MOVEMENT)..
Maybe you are looking for
-
Can i use more than 1 account on my Macbook pro?
I have a macbook pro (wich i'm now gonna keep) Can i create and use 2 different App store accounts on the same mac?? And use Aplications like pages from 1 account, and iMovie from the second at the same time ??
-
Multiple iPhones on same AppleID and iTunes
Can I have 2 different iPhones with 2 different phonenumbers connected to the same AppleID and iTunes? If yes, should I be aware of something. If no, how do I do?
-
Multiple ipods on 1 computer - sync. v. manual
Hello! I set up an itunes account for my wife's nano on our computer where I already have an itunes account. I have created a separate itunes account for her, and I have copied my libarary onto her account. Once I plug in her nano into itunes, I get
-
Javascript maildoc issue with Adobe Reader 9.5
Good morning all, I am trying to find a possible answer to an issue I have been given regarding the maildoc javascript we are using in one of our forms. We are on Windows XP, Adobe Reader 9.5 and Outlook 2010. We generate purchase orders within SAP a
-
My GTX 580 OC will not drop the core clock frequency when idle
The model is N580GTX-M2D15D5/OC . I have read some reviews said that the GTX580 drops the core clock down to about 50MHz when idle. But my card will always stay at 823MHz. Is this a issue or it's just working as intended? Can i have the clock auto-tu