Billing Type G2 configuration steps
Hi,
Can someone guide me through the configuration steps for creating a billing document type G2 for the following requirement.
We have got negative quantity in the Invoice Receipt and for it we wish to post the Credit Memo (G2), and we will post this credit memo with reference to the Sales Order. To achieve this solution i would like to have assistance on :
1. How to configure the billing type "G2"
2. How can this document type be listed in billing due list via VF04 ?
3. How will the financial postings will effect after this invoice is generated ?
Appreciate your kind help.
Thanks
Krishna
Dear Krish,
You are using credit memo type G2, which is not specifically made for third party item. Because the copy control settings that you need for this transaction are not available in OR-G2. In copy control OR-G2 at item category level TAN-G2N see the field billing qty.
For third party scenerio, it should be 'IR qty/GI qty minus billed qty'.
Now see the settings for OR-G2S copy control settings. TAS-TASG item category Billing qty field.
As I told you before also. If you don't want to use G2S document, make a copy of it & then use it for credit processing. But don't make these changes for G2 doc type, because it is used for other process specifically return order, invoice correction request & ... Changing in G2 will have adverse effects.
You can't see status in order document as incomplete, but a negative Invoice Receipt Creates a billing index for credit memo.
And then you can create the credit memo for customer. This is again based on the copy control settings.
You can use report SDMFSTRP to create a list of all sales orders with third-party order items for which there are discrepancies between the quantities ordered, invoiced, canceled, or credited in Sales and the quantities ordered, invoiced or credited in Purchasing.
To run this report, proceed as follows:
Choose Tools -- ABAP/4 Workbench on the initial screen.
Choose Development -- ABAP/4 Editor.
Enter the report name SDMFSTRP in the program field and choose Execute.
You reach the selection screen.
Enter the interval of sales orders and the time period which you want to monitor.
Choose Program-- Execute.
Best Regards,
Ravi
Similar Messages
-
Is any SD/MM Configuration step by step procedure available in the market?
Dear fellow SDN's,
Please give me a guide on
1. Where to start SD learning?
2. How to proceed to become a strong SD consultant.
3. Is any SD/MM configuration procedure pdf / Document available in the market?
I have an ECC 6.0 remote connectivity.
Your valuable advice appreciated and allow to earn good credit.
Thanks in advance.
Regards.HI Stockton,
1. Try to start with the Basic Concepts of SD which are given Below:
SD FLOW/ OVERVIEW:
Sales
Inquiry - A customers request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.
Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.
Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.
The sales area that accepts the inquiry is responsible for completing the agreement.
Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.
b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).
c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.
Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
Sales Order Management Transactions
SALES ORDER PROCESSING
Creating Sales Order - VA01
Maintaining a Sales Order - VA02
Displaying a Sales Order - VA03
Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1
Display List of RMAs by Customer - VA05
Confirm RMA Goods Receipt - VL02
Generate list of open return orders for deletion - VA05
Display Customer returns eligibility - MCSI
Removing a Billing Block (Approving Credit/Debit Requests) - V.23
PRICING MASTER DATA
Create Pricing - VK11
Creating a Sales Deal - VB21
Maintaining a Sales Deal - VB22
Displaying a Sales Deal - VB23
Maintaining Prices - VK12
Displaying Prices - VK13
MATERIAL MASTER DATA
Creating Material Substitution Master Data - VB11
Maintaining/Deleting Material Substitution Master Data - VB12
Displaying Material Substitution Master Data - VB13
Creating a Bundled Master - MM01
Creating a Sales BOM - CS01
Maintaining a Sales BOM - CS02
Displaying a Sales BOM - CS03
CUSTOMER MASTER DATA
Creating Partner Records - XD01
Maintaining Customer Master Data - XD02
Displaying Customer Master Data - XD03
Deactivating a Partner - VD06
CUSTOMER CREDIT INFO
Creating/Maintaining New Customer Credit Information - FD32
Displaying Customer Credit Information - FD33
Blocking or Unblocking a Customer - VD05
SHIPPING
Creating a Delivery - VL01N
Displaying a Delivery - VL03N
Changing a Delivery - VL02N
Shipment Inquiry / Display - VT03
Adjusting Transfer Order - Confirmation Quantity - LT12
Collectively Confirm Transfer Order - LT25
Batch Shipment Confirmation - VL19
PGI Reversal Cancellation - VL09
Creating Service Provider/Carrier Master Data - XK01
Maintaining Serive Provider/Carrier Master Data - XK02
Displaying Service Provider/Carrier Master Data - XK03
Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02
IDoc Inquiry - WE02 / WE05
BILLING
Invoicing a Customer Shipment - VF01
Reprinting an Invoice - VF31
Releasing a Sales Order for Billing - V.23
Creating an Invoice by Using the Billing Due List - VF04
Checking Open Billing Documents - VF05
Create Credit/Debit Memo - FB01
A/R
Controlling Total Debit/Credit bkgs - F.03
Generate FI Account balance - F.08
Generate Month-to-date Inv. register - F.02
Process payments - FBZ1
Rqst Individual Customer Corresp. - FB12
Generate Customer Correspondence - F.61
Enter Batch totals under Control ttl - FB07
Display G/L Acct. totals - FBL3N
Reverse Posted Amounts - FB08
Customer Refunds - FBL6
Customer Refund to other than Payer - FB05
Clearing Debit/Credit on Cust. acct. - FB1D
Customer Balance in Local Currency - F.23
G/L Account Balance Report - F.08
Create Invoice - legal entity adjust - FB01
Generate Cust. Acct. statements - F.27
Generate Dunning Letters - F150
Generate Billing Due List - VF04
Generate Blocked Billing Doc list - VFX3
Inq. via Credit Release Screen - VKM1
List orders by partner - VA05
Past Due invoices by customer - FD11
Check number info by G/L account - FBL3N
Display customer Line items - FBL5N
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
he configuration differs from scenario to scenario & requirement of the client.
Interesting &important link to learn much more about configuration & business process is as under:
Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.
SD FLOW
SD Flow Cycle:
INQUIRY ( VA11)
|
QUOTATION (VA21)
|
PURCHASE ORDER (ME21)
|
ORDER CONFIRMATION (VA01)
|
PICKING LIST (VL36)
|
PACKING LIST - (VL02, VL01)
|
SHIPPING (VT01)
|
INVOICE (VF21, VF01)
|
AR
2.Hope aware that SAP- SD itself the Big one.try to Explore the various Scenarios in SD and be Stong in Some Areas like Pricing, Intercompany Billing, Third Party Sales, LSWM, EDI Etc.,
3.The link between SD and MM: -
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availability check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
SD INTEGRATON WITH MM
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availability check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM
In Pricing we would want to determine the cost of the product
thru VPRS Condition Type. This cost of the material is
picked from the Material Master. How this happens is, if
we would want to determine this cost VPRS in the Sales Order
for Profitability purpose then , all those Item categories
that can appear in a sales order must be activated for
Determine Cost Check box in customizing. Thats one of the SD
MM Integration.
Please go through the below Link,
http://sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
Hope Clarifies your doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Give me the Configuration steps for intercompany billing and third party s
Hi Gurus,
Give me the Configuration steps for intercompany billing and third party sales and give me a brief description with examples.
Regards,
YSRDear YSR
Check the links
[Cross Company Configuration|http://help.sap.com/bp_bblibrary/500/Documentation/J62_BB_ConfigGuide_EN_DE.doc]
[Third Party Without Shipping Notification|http://help.sap.com/bestpractices/BBLibrary/html/J55_ThirdPartyWOSN_EN_US.htm]
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1)
After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination
ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F
Step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
thanks
G. Lakshmipathi -
Guide in configuring number range by billing type in SD
Hi gurus,
Hope you can assist me in configuring number ranges by billing type (e.g. F2, G2, L2, etc) in SD. Our Accounting people find it hard to account the completeness of the transactions because we are only using one range for the RV (SD docs). We would like to setup a separate series per billing type.
Your immedaite assistance is highly appreciated.
FrancesDear Frances,
1st Part
Go to, T. Code: SNRO
Insert, Object: RV_Beleg
and Click Tab: Number ranges (just above the Field: Object)
On to next screen, Click Tab: Intervals (with pencil-icon)
Here, maintain your Number ranges, that you wanna assign to your Billing Doc. Types, i.e. F2, G2, L2 etc..
2nd Part
Go to, T. Code: SM30
Insert, Table/View:
and click Tab: Maintan (down, at screen)
On to next screen, maintain entries as:
Sales Org + Dist. Chnl + Sales Doc. Type (i.e. Billing Doc.) + IntNR (as maintained in 1st Step)
Best Regards,
Amit -
Configuring output types to billing types - billing document
Hello Experts,
i want to configure output types say O1, O2 to the billing types F1 and F2. Can you pls explain how should we do that. Whenever we create an invoice, i want to trigger my form...
i'm not into functional, am an abaper
Thanks in advance
ShekharHi
If You have create new condition type , then you need to do following configuraions
Can use T- code NACE or SPRO Sales & Distr-Basic Functions-Output DeterBilling Documents
1. Otput type assignment to Partner Function can be different from BP ( Since New Condition Type so requirement must be different , otherwise std o/p tpe RD00 can be used).
2.Assign / Include the condition type in the Output procedure V10000.
3. Assign the Procedure to your billing document .
4. T code vv31, maintain condition record for new o/p type
Regards
Rohit
Edited by: bahlrohit1 on Jul 8, 2009 12:03 PM -
Bill of ladding output configuration steps
Hi Experts,
Please let me know the detailed configuration steps for the bill of ladding output? I want this to be configured in the shipment completion.
Appreciate your help.
Thanks.
with regards,
MuthuDear Muthu
Please go thru the thread
[Bill of Lading for Shipment |Re: Bill of Lading for Shipment]
thanks
G. Lakshmipathi -
Risk Mgmnt COnfiguration steps
Hello Friends
Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
Regards
Sumanth.GururajHi,
The configuration steps for risk management
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.
Credit Management Reports
The following table provides an overview of all the reports that are available for credit management:
Program Function
RFDKLI10 Customers with Missing Credit Data
Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
RFDKLI20 Reset Credit Limit for Customers
Resets the credit limit information in the control areas.
RFDKLI30 Credit Limit Overview
Lists the central and control area data for each customer.
RFDKLI40 Credit Overview
Provides a comprehensive overview of the customeru2019s credit situation.
RFDKLI41 Credit Master Sheet
Displays and prints the customer master data for an individual account that is needed for credit management.
RFDKLI42 Early Warning List
Displays and prints customers in Credit Management who have been listed by the credit check as critical.
RFDKLI50 Credit Limit Data Mass Change
Changes all the credit management master data together.
RFDKLIAB Display Changes to Credit Management
Displays the changes to credit management master data for all accounts.
RVKRED06 Check Blocked Credit Documents
Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
RVKRED77 Reorganize SD Credit Data
Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
RVKRED08 Checking sales documents which reach the credit horizon
Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
RVKRED09 Check Credit Documentation Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88 Simulating Reorganization of SD Credit Data
To run a report:
1. Choose System ® Services ® Reporting.
2. Enter the name of the report.
3. Choose Program ® Execute.
4. Enter your selection criteria.
5. Choose Program ® Execute or Program ® Execute and print.
SAP SD Credit Management Tcodes
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Dayu2019s oldest item
No of days allowed for overdue or payment terms.
Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be re-blocked again by the system. The system only re-blocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document date is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
SIMPLE CREDIT CHECK:
Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value: Sales Order has been saved but not delivered
Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1, 00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options: A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Category: Based on the risk Categories Company decides how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003): AVERAGE CREDIT
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value: Which is save but not delivered
2) Open Delivery Doc.Value: Which is delivered but not billed
3) Open Billing Doc.Value: Which is billed but not posted to FI
4) Open Item: Which is transferred to FI but not received from the customer.
DYNAMIC CREDIT CHECK:
1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the last 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check (0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
User Exits For Credit Checks And Risk Management
Credit Check
I hope this will resolve your issue
Thanks
Anil Hooda -
Hello SD Guru's
I want to configure sales info system to my client.
Please let me know the step by step configuration steps needed for this.
Heighly Rewarded,
Reg,
krishna.sapsd ya.comhi
1.create information structure by selecting the key figures and characteristics. After creating the information structure u must activate and generate.
2.include updating rule for information structure. After including the updating rule the information structure u must activate and generate
3.select the updating rule is whether for day, week, month, or year by double clicking on the information structure.
4.Maintaining all seetings ie; customer statistics group, materialstatistics group, sales document, sales item, billing document, and assign all these to sales document type, sales item, billing type,
5.Assign sales area to updating rule.
6.check the sales area whether all settings are maintained or not.
7.maintained customer statistics group in the customer master record, and material statistics group in the material master record.
8.After all the settings use T.c. MCSI enter the sales area customer material and see the results, now u get the report or sales of a particular customer or organization.
Note: Before doing the last step create a sales order, delivery, AND billing.
for details check this link
http://help.sap.com/saphelp_47x200/helpdata/en/c1/37544e449a11d188fe0000e8322f96/frameset.htm
reward points if helpful
regards
chetan -
Billing Type - Proforma Excise Invoice
Dear friends,
The flow I am using for billing from excisable unit:
VA01 >2. VL01N(PGI)> 3. VF01 (Proforma Inv) --> 4. J1IIN (Excise Inv) --> 5. VF01 (Comm Inv)
1.For generating the Proforma Invoice I am selecting the Billing Type - Excise Invoice (VF01). Is this the correct procedure or do I need to create a copy of the Deliver related Proforma?
2.If the above (Billing Type - Excise Invoice (VF01)) process is correct what is the doc type for the Proforma and where are we configuring the no ranges for the Proforma invoice?
3.The document type for Excise Invoice is JEX and are we using the same for Proforma as well.
Thanks
IsaacHi
You Can use the F8 billing type for proforma invoice you can also use JEX
Number ranges can be defined in VN01
regards -
OBIEE 11g installation failed multiple times at Distributing Repository Configuration Step
Hi,
I am getting the following error during the Distributing Repository Configuration step in the OBIEE 11g 11.1.1.7 enterprise installation in Windows 8 system.
Severe: Element Type:Domain
Element id: null
Operation result: failed to obtain domain file lock
Detail Message: java.util.concurrent.timeoutException.Timeout;
waiting for lock: Domain config lock;
c:\OBIEE\MIDDLE~1\USER_p~1\domains\EAM_DO~1\config\FMWCON~1\biee-config.lock;[121 secs]
Step Distributing Repository failed
Configuration Action 'Distributing Repository' has failed. Please check logs for details.
Step Distributing repository failed
I checked another blog for this https://forums.oracle.com/thread/2565716 and even there the explanation doesn't convince me.
I tried to look at the Locale of my system where I am installing and I could see it is using Eng-Us by default. One way suggested to check the Unicode format from the web browser and I could check that too to be UTF-8 as suggested by someone on some other blog.
I checked in the logs too as suggested by the Installation dialogue box but it didn't seem much conclusive too.
Here is the snapshot of the log file which I could found.
INFO: Current Inventory:
Oracle Home: OraDb11g_home1
This Oracle Home has not been changed in this session.
Oracle Home: OH1858390736
This Oracle Home has not been changed in this session.
Oracle Home: OH440082373
This Oracle Home has not been changed in this session.
Oracle Home: OH440082374
This Oracle Home has not been changed in this session.
Oracle Home: OH1597391518
This Oracle Home has not been changed in this session.
Oracle Home: OH1285215443
This Oracle Home has not been changed in this session.
INFO: Ending the inventory Session
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
Can someone please help me with this since I am stuck with for quite some time now.
Is there any way to check in command prompt to check the locale as required by the system.
What could be the issue here?
Thanks,
NitinHi all,
We are able to resolve the above issue with the below solution.
Root cause of the issue:
You may have a temp directory in the path C:\Documents and Settings\user_name\Local Settings\Temp. You got the above mentioned exception because of the temp directory path having spaces_+ in it.
Solution:
1. Create a new directory called TEMP in a different location for ex: C:\TEMP
2. Now, Right click on My computer --> Properties --> Advanced --> click on Environment Variables.
3. You should be having TEMP and TMP as variables under user variables section pointing to the C:\Documents and Settings\user_name\Local Settings\Temp path.
4. Edit the TEMP and TMP variables and mention C:\TEMP in the variable value.
5. Deinstall and re-install OBIEE 11g.
Happy OBIEE 11g installation!!
Thanks,
Rajesh Gurram -
Assignment of Step type and CR step for MDG_S
Hi
This is in continuaton for thread MDG_S workflow.
I original issue which is for MDGS when I assigned WS543000005 to CR type and sumitted CR goes no where,
As as per SWEL it shows No Reciver Found enen though GET_AGENT table is maintained.
In another system I found that WS531000044 is assigned ti CR Type Then I tested it and found that CR creates Work Items also upto final processing.
as per below
Before CR Submission : CR status is 02: Changes to be executed
After CR Submission : CR status is 01:To be considered and Approved
After CR Reviewer approves : CR status is 09: Dependant Data to be processed /Approved
After Purchase reviewer Finalize processing :CR status is 09: Dependant Data to be processed /Approved
After Finainace reviewer Finalixe processing :CR status is 09: Dependant Data to be processed /Approved
Now I can not see CR any where even though CR step 04 and 04 assigned to my user ID
I have some questions as Description in Define Change Request Steps is not Mataching with description in GET_AGENT desesion table.
Also it is observed that step 80 is not assigned to WS531000044 in IMG node Define Change Request Steps but it can be seen in GET_AGENT decesion table and step no 06 and 07 does not appears in GET_AGENT decesion table ( In edit mode).
Can you explain from where assignment of CR steps to CR type in desion table are taken ino accout ?
Why description is not matched for steps under IMG and in decesion table?
Can you explain me releationship between CR step and step type,CR Status and where they \maintained in IMG and how proceeses modelling is diffenent t for determination of Next CR step in case of WS531000044 ?Please keep in mind that "hard-wired" workflow templates are just that: hard-wired. This means that a specific workflow template (for example WS53100044) will always have the same number of steps, each step will always have the same type and number, agents will always be assigned in the same way, and those can't be altered by configurations. To understand each workflow template's behavior, you can either open that template in transaction PFTC or SWDD, or alternatively, read the exact behavior in SAP Help documentation. You basically need to google the workflow template number and you should be able to find the description of each template's behavior (by the way, the number you type has an extra zero so if you can't find a match on Google, you will know why ).
Now, the assignment of CR steps to CR type is done in the workflow template itself and NOT in the decision table. See the first screenshot:
The step number above "should" correspond to what is in the configuration table (for readability and consistency of documentation purposes). However, if for some reason, it does not, the hard-coded value is the value that will actually be considered. So, in technical terms, the assignment of step numbers in MDGIMG has no influence on how the workflow template will behave. Again, the main purpose is for the corresponding description in the step number configuration table to show on the CR window.
The other thing is the step type. A step type purpose is mainly to indicate what set of buttons will show at the top of the CR window. The fact that step types are represented by numbers confuse a lot of people with step numbers. I would have personally preferred if step types were a 2-char field so that a clear distinction can be made between step types and step numbers. In any case, buttons on the CR correspond to actions and you can see in MDGIMG that you can assign step types to actions. SAP delivers a pre-defined set of step types and associated actions. Those must NOT be altered because they could break the standard workflow templates. However, you can create your own custom step types and link them with as many actions (standard or custom actions) as you like. But again, you can't assign those custom step types to hard-wired workflow templates. You can only use them in your custom workflow templates or in the rule-based workflow.
Now, the question is how does the hard-wired workflow know what step type to use. The answer is easy: you can either find that in the SAP Help documentation or in the workflow template definition in transaction SWDD. For the above screenshot, the step type is 2. You can find that if you double-click the task ID TS75707980 (or display it using transaction PFTC) and look in the "Cntainer" tab. In this case, this task will ALWAYS have type 2. Other tasks are assigned different step types or are more dynamic in the sense that they expect the step type to be passed from the main workflow template calling them. For example TS53200002 will always have type 7, TS60808005 will always have type 5, and TS60807954 accepts the step type dynamically. This last one is the one used in the rule-based workflow (hence it has to read the step type configured in the decision table).
I hope this answers you question. You definitely need some level of workflow design/build knowledge in order to be able to completely understand all of this. Hopefully, this gives you a good starting point. -
Billing type..VPRS
Hi Experts,
I have mapped VPRS to one Value fiels for COGM.
Client is giving free of goods to customers, for that no revenue is generating only std cost is picking for condition type VPRS,the same amount is going to CO-PA, But he dont want that amount to CO-PA under COGM.
He want that amount under selling expenses, for that perpose it is hitting one GL account in FI(not COGS GL account)
he is using only one billing type for all.
he is using different item catagiry.
Pls advise how can i avoid COGM to CO-PA in sample orders?
If there is any possibility by using Materila numer or item category?
Thanka
ChanduHi,
As you are stating that there is no separate Billing Type, the below solution may meet your requirement:
u2022 Create a new Condition Type (ZPRS) same as VPRS with Condition Class u201CAu201D (Rebates and Discounts) instead of u201CBu201D (Prices). Give u201Cminusu201D sign in the Condition Type setup.
u2022 Assign ZPRS in the step below VPRS and make it Statistical in the Pricing Procedure.
u2022 Give a Requirement Routine such that when the Order Reason for Free of Charge is active, ZPRS is also active (need an ABAP consultant).
u2022 Assign ZPRS to same Value Field as VPRS in KEI2. This will nullify the value in COPA for Free of Charge as value from VPRS is +ve and same value from ZPRS is u2013ve.
Regards,
Kiron Kumar T. -
Config of billing type G2 for Revenue Recognition
Hello Experts.
I have a situation where I need to configure billing of credits for revenue recognition.
For normal builling we have copied doc type SO to ZBCS and added ZTAD item category (copied from TAD) for the RR.
To do this for credits I copied doctype CR to ZBCR and assigned ZTAD item category to it.
When billing the ZBCR not I get the message "Item category ZBCR ZTAD cannot be invoiced with billing type G2".
How can G2 be configured to allow this?
This is G2's current setup.
Billing Type G 2 C red tM e m o Created by
Number systems
No.range int.assgt. 19 Item no.increment 0
General control
SD document categ. O C re dit m emo Posting Block
Transaction group 7 B il lin g doc um ent s Statistics
Billing category
Document type DG C us tom er cr ed it me mo
Negative posting N o neg at ive p ost in g
Branch/Head office C us tom er =Pa ye r/B ra nch =s old -t o p ar ty
Credit memo w/ValDat N o
Invoice list type
Rebate settlement Rel.for rebate
AcctDetermProc. KOF I0 0 A cco unt De e rm n ato n
Doc. pric. procedure
Acc. det. rec. acc.
Acc. det. cash. set.
Acc. det. pay. cards
Output/partners/texts
Output determ.proc. Z10 00 0 B il lin g Out pu t Application V 3
Item output proc.
Output Type
Header partners FK B iln g D ocu m en t
Item partners FP B il lin g Ite m
TextDetermProcedure 03 Invo c e hea de r
Text determ.proc.itm
Delivery textHi,
You may be maually given the PR00 in ZBCR. But in your copy control (VTFA) --> item category ZTAD --> pricing type, you may be maintained B (Carry out new pricing).
If you maintain B, you have to change it to "D ".
When you maintain B, the system will search the Pricing again in Credit memo. All manual prices will be lost.
Thanks
M. Lakshmi Narasimhan -
GC install fails on OMS Configuration step with NodeManager
I'm trying to install OEM Grid Control and I'm having some problems getting past the OMS Configuration step in the installation. I'm not very familiar with Oracle products. I've completed all the configuration steps listed in the documentation and in order to resolve an earlier problem, I deleted the Keynectis and Telesec certificates from the cacerts java keystore. NodeManager is being run as a service, though I think the configuration process is launching a new instance because it can't connect to the service. I've also been unable to connect to the service through the WLST nmConnect function, though it's possible my parameters are incorrect. If the only problem is that GCDomain is not registered in the nodemanager.domains file, I'm not sure what I'm doing wrong, because I put it in the nodemanager.domains file located at C:\Oracle\Middleware\wlserver_10.3\common\nodemanager:
#Domains and directories created by Configuration Wizard
#Fri Apr 22 15:23:16 EDT 2011
wl_server=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\wl_server
medrec-spring=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec-spring
GCDomain=C\:\\Oracle\\gc_inst\\user_projects\\domains\\GCDomain
medrec=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec
note - the file paths are correct and use escaped slashes where appropriate, but this message board system is turning the last double backslash into a line break. I can't find any html solution that works, so just take my word for it
I restarted NodeManager after making the change as well. Any help would be appreciated. Thanks.
Details:
Machine - Windows Server 2008 x64
DB - 11gR2
WLS - 10.3.2
GC - 11.1.0.1
Install Log:
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: This Exception occurred at Fri Apr 22 15:23:20 EDT 2011. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: weblogic.nodemanager.NMConnectException: Connection refused: connect. Could not connect to NodeManager. Check that it is running at win2008x64-2:7,401. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.socketConnect(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.Socket.connect(Socket.java:525) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyReflectedFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyMethod.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.invoke(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx2.nmConnect$3(<iostream>:118) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx2.call_function(<iostream>) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx41.startNM$1(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py:20) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx41.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx39.f$0(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py:74) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx39.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.Py.runCode(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.util.PythonInterpreter.execfile(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.WLST.main(WLST.java:131) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.WLST.main(WLST.java:29) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Fri Apr 22 15:23:20 EDT 2011 Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Node Manager is down starting it Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Not connected to Node Manager Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Launching NodeManager ...
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Properties: {ListenAddress=win2008x64-2,ListenPort=7401,NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239,StartScriptEnabled=true,StartScriptName=startEMServer.cmd,}
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Command: C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin\javaw.exe -classpath "C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\rt.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\i18n.jar;C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.2.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\lib\ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1\lib\ant-contrib.jar;C:\Oracle\Middleware\oms11g\sysman\jlib\emConfig.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.policies_11.1.1\wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\org.apache.commons.digester_1.7.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.auditprovider_11.1.1\jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar" weblogic.NodeManager "-v"
Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <INFO> <Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <WARNING> <Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:22 PM> <INFO> <Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true> Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:22 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <WARNING> <Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings.> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings. Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties'> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Node manager v10.3 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Configuration settings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenAddress=win2008x64-2 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenPort=7401 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenBacklog=50 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: SecureListener=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: AuthenticationEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NativeVersionEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: CrashRecoveryEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: JavaHome=C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptName=startEMServer.cmd Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptName= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.log Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLevel=INFO Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLimit=0 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogCount=1 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogAppend=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogToStderr=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFileEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StateCheckInterval=500 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: QuitEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Interface= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NetMask= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: UseMACBroadcast=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainRegistrationEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Domain name mappings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.SSLListener run Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Successfully launched the Node Manager. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager process is running independent of the WLST process. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Exiting WLST will not stop the Node Manager process. Please refer Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: to the Node Manager logs for more information. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager logs will be under C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:41 PM> <WARNING> <Configuration error while reading domain directory> Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'GCDomain' at 'C:\Oracle\gc_inst\user_projects\domains\GCDomain' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file. Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:257) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:224) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:108) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:70) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at java.lang.Thread.run(Thread.java:619) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
...I have a JDK already installed, but isn't JRockit being used by NodeManager in this case? Does NodeManager need to run on the JDK?
Regardless, I tried changing JavaHome in the nodemanager.properties file to the JDK/jre directory, but the log file still has the original path. The log seems to indicate that the process thinks that NodeManager is down because it can't connect, so it launches a new instance and uses default configuration parameters, which naturally wouldn't have my changes to the nodemanager.domain or nodemanager.properties files.
Also, the log says it can't connect to NodeManager at win2008x64-2:7,401. I'm not sure why there's a comma in there, but by the time this configuration step fails, there is a javaw.exe process listening on port 7401 and if I retry the step without killing it, the step will fail earlier because the port is already bound. -
Billing type in BAPI_SALESORDER_CREATEFROMDAT2 function Module
Hi,
Am creating sales orders through my program using the Function Module "BAPI_SALESORDER_CREATEFROMDAT2".
I have data(fields) for which i have to create a Sales orders.
I have mapped all the fields to the structures in the FM except Billing Type, I couldn't find where to map this "billing type" field in the Function Module.
I want to know into which structure's field in the above FM should this Billing type to be mapped.
Thanks,
Adithya M.Why do you need to pass the Billing Type when you are creating the Sales Order? Only Sales order type is required in the sales order creation.
Based on the configuration maintained in the sales order, if future, system will create the specific type of delivery and Specific type of Billing document.
Regards,
Naimesh Patel
Maybe you are looking for
-
RSS Feeds on Yahoo Front Page/My Yahoo are no longer loading. Please help!
After "fixing" my installation of Firefox I am unable to load any RSS feeds onto My Yahoo Front Page! They are all gone. Please help me to recover these important feeds. They are my only source of News every day.
-
"Not Verified" WIFI connection certificate
Hi everybody! I am dealing with a new setup for my company to use WPA2 Enterprise using Radius. My actual configuration works fine but I receive an alert the first time that I try to join to the network with my Iphone (client). The certificate that
-
Syncing multiple iPhoto and Facebook albums
Hallo everyone... I'm using iPhoto '09 on 3 Macs under the same LAN. Every Mac is set to login to same Facebook account and post photos. In this scenario I have: • Mac A created a album and shared to Facebook • Mac B created a album and shared to Fac
-
T3i- Movie recording has stopped automatically
Hi, guys. I've never had this problem with my T3i/SD card until tonight, and I'm not sure what the problem is because I have the Sandisk Extreme Pro, 32 GB SD card that reads 95 MB/s. What could be the problem? The video stops recording after about 5
-
New look utilizes a dark gray scroll bar on a black background. Older monitors (non HD) do not show it at all and tablet PC can't be viewed in sunlight. Really Spotify you didnlt think about making it a more contrasting color.