Friday, October 3, 2014

Devyaa Aartikyam



Alikul komal baale dhrut moutik maale Stan yug nirjit taale kshiraam-budhi baale Kaashmira-ankit bhaale naashit bhav jaale Lilaa mardit kote sharanaagat paale
Jay Devi jay Devi jay maatah kamale Drut jaambu nad vimale sur nut pad kamale Jay Devi jay Devi
Kamal dalaayat nayane shashi nibh shubh vasane Simha viraajit gamane hiraavali radane Muni jan virchit namane krut raakshash kadane Kokil manjul gadane Vishnu-rah sadane II Jay Devi…II
Naag-aadi ankit mastak bhuvan-aavan sakte Praashan bhaajan khet-aadi-aayudh kar yukte Krut kar vir nivaase ripu mardan sakte Shuk naashaa samanaase taarit nij bhakte II Jay Devi…II
Adhar vinir-jit bimbe vishva stut rupe Pruthu-tar chaaru nitambe krut daanav kope Bhru jit manmath chaape nij jan hrut taape Daaji jyotir vidvaan prana-mati hrut taape II Jay Devi…II

Wednesday, July 9, 2014

Why i am not able to float easily

  1. The distribution of body tissues on a unique physical structure causes each individual to float differently. When adipose tissue is concentrated more in one part of the body (e.g., around the thighs and hips of "pear-shaped" women) the center of buoyancy moves closer to the center of gravity reducing the rotational sinking effect in the lower part of the swimmer. Such individuals would need to devote less effort to force production to streamline the total shape. Conversely, swimmers with very little fat below the center of gravity, but with some above, will sink markedly. They will need to work harder with kicking to maintain streamliSourcene while swimming.

Wednesday, April 9, 2014

Conversion Strategy

PO


This conversion is from one inventory organization to another inventory organization

We create a new line with the outstanding quantity and cancel the earlier line.
 This will close the old line for receiving but the line will still be open for invoicing.


Where the quantity billed is less than the quantity received. : No issues. Invoice can still be matched

Where the quantity billed is more than the quantity received. :
Unmatch the invoice before conversion and match it after conversion.

Friday, March 21, 2014

Back Order

Order Management and Shipping Execution has two types of   Backorders.

Back-orders caused by Pick Releasing (PR)  order lines when there is no or not enough stock available.

And back-orders caused by shipping less, at Ship confirm, than what was released.



A. Backorders after Pick Releasing with Insufficient Stock

Pick Release will process all order (more correctly shipping) lines that you selected when
submitting PR.  It will create move order lines for each line, whether there is stock available or not.
You (or the system) will however, not be able to (auto) detail and (auto) Pick Confirm the    
lines where there is not enough stock available.  In R11i, you cannot switch off reservations
for PR.  Also, the system will not print pick slips for lines that are not detailed.
 
The delivery line, which was 'Ready to Release' before running PR will be split into a quantity
 that was available for picking and a unavailable quantity.  The first delivery line will become
status ‘Released’ (Pick Confirmed), the second 'Submitted for Release' (Move Order created,
but not confirmed).  In the latter case, the ‘Details Required' status is checked.  The order line will
 not split at this point, but receives a 'Picked partial' status.  After Ship Confirming the Released
delivery line, the original order line will be split into a 'Shipped' and a 'Submitted for Release' line
 (unless the shipped quantity falls within the under shipment tolerance).  The latter will be available
 for Pick Release as a 'Backorder' as soon as there is stock available.  On the sales order, there is
no order or workflow status called 'Backorder'.  You will not really see any difference
between a scheduled order line that was never released and a backordered line.  
Pick Release is able to distinguish between the two, because it allows you to release them
separately.

B. Backorders Caused by shipping less than what was Released

Before Ship Confirming a Released (Pick Confirmed) delivery line, you have theoption to update the 
shipped quantity.  If the shipped quantity is less than the picked quantity, you have can either 
designate the remaining quantity as
'Backordered' (meaning the quantity was lost somewhere along the picking/staging process) or 
leave it in staging in to assign it to a different delivery (i.e. truck was full and wait for next pick up).
At Ship Confirm, any staged quantities will be split off in a separate delivery line that is
immediately ready to be shipped in a subsequent delivery.  A backordered quantity will remain 
noted on the same delivery line.  Only when the original delivery line is interfaced through       
Inventory Interface/Order Management Interface, will the order line be split into a line for the 
shipped quantity and a new line for the backordered quantity (Awaiting shipping).  This enables 
you to pick the remaining quantity again in order to fulfill the complete order quantity.  This split 
will only happen if the backordered quantity is greater than the Under Shipment Tolerance.

Order Management Flows and Workflow Status

Friday, March 14, 2014

Bulk Collect EXCEPTION

Source




SQL%BULK_EXCEPTIONS(i).ERROR_CODE – Holds the exceptions error code.
The total number of exceptions can be returned using the collections COUNT method, which returns zero if no exceptions were raised.  The save_exceptions.sql script, a modified version of the handled_exception.sql script, demonstrates this functionality.
save_exceptions.sql
SET SERVEROUTPUT ON
DECLARE
  TYPE t_tab IS TABLE OF exception_test%ROWTYPE;
  l_tab          t_tab := t_tab();
  l_error_count  NUMBER; 
  ex_dml_errors EXCEPTION;
  PRAGMA EXCEPTION_INIT(ex_dml_errors, -24381);
BEGIN
  -- Fill the collection.
  FOR i IN 1 .. 100 LOOP
    l_tab.extend;
    l_tab(l_tab.last).id := i;
  END LOOP;
  -- Cause a failure.
  l_tab(50).id := NULL;
  l_tab(51).id := NULL; 
  EXECUTE IMMEDIATE 'TRUNCATE TABLE exception_test';
  -- Perform a bulk operation.
  BEGIN
    FORALL i IN l_tab.first .. l_tab.last SAVE EXCEPTIONS
      INSERT INTO exception_test
      VALUES l_tab(i);
  EXCEPTION
    WHEN ex_dml_errors THEN
      l_error_count := SQL%BULK_EXCEPTIONS.count;
      DBMS_OUTPUT.put_line('Number of failures: ' || l_error_count);
      FOR i IN 1 .. l_error_count LOOP
        DBMS_OUTPUT.put_line('Error: ' || i ||
          ' Array Index: ' || SQL%BULK_EXCEPTIONS(i).error_index ||
          ' Message: ' || SQLERRM(-SQL%BULK_EXCEPTIONS(i).ERROR_CODE));
      END LOOP;
  END;
END;
/
SET ECHO ON
SELECT COUNT(*)
FROM   exception_test;
SET ECHO OFF
The FORALL statement includes the SAVE EXCEPTIONS clause, and the exception handler displays the number of exceptions and their associated error messages.  The output from the save_exceptions.sql script is listed below.
SQL> @save_exceptions.sql
Number of failures: 2
Error: 1 Array Index: 50 Message: ORA-01400: cannot insert NULL into ()
Error: 2 Array Index: 51 Message: ORA-01400: cannot insert NULL into ()
PL/SQL procedure successfully completed.
SQL> SELECT COUNT(*)
  2  FROM   exception_test;
  COUNT(*)
----------
        98
1 row selected.
SQL> SET ECHO OFF
As expected the test table contains 98 of the 100 records, and the associated error message has been displayed by looping through the SQL%BULK_EXCEPTION collection.
If the SAVE EXCEPTIONS clause is omitted from the FORALL statement, execution of the bulk operation stops at the first exception and the SQL%BULK_EXCEPTIONS collection contains a single record.  The no_save_exceptions.sql script demonstrates this behavior.
no_save_exceptions.sql
SET SERVEROUTPUT ON
DECLARE
  TYPE t_tab IS TABLE OF exception_test%ROWTYPE;
  l_tab          t_tab := t_tab();
  l_error_count  NUMBER; 
  ex_dml_errors EXCEPTION;
  PRAGMA EXCEPTION_INIT(ex_dml_errors, -01400);
BEGIN
  -- Fill the collection.
  FOR i IN 1 .. 100 LOOP
    l_tab.extend;
    l_tab(l_tab.last).id := i;
  END LOOP;
  -- Cause a failure.
  l_tab(50).id := NULL;
  l_tab(51).id := NULL; 
  EXECUTE IMMEDIATE 'TRUNCATE TABLE exception_test';
  -- Perform a bulk operation.
  BEGIN
    FORALL i IN l_tab.first .. l_tab.last
      INSERT INTO exception_test
      VALUES l_tab(i);
  EXCEPTION
    WHEN ex_dml_errors THEN
      l_error_count := SQL%BULK_EXCEPTIONS.count;
      DBMS_OUTPUT.put_line('Number of failures: ' || l_error_count);
      FOR i IN 1 .. l_error_count LOOP
        DBMS_OUTPUT.put_line('Error: ' || i ||
          ' Array Index: ' || SQL%BULK_EXCEPTIONS(i).error_index ||
          ' Message: ' || SQLERRM(-SQL%BULK_EXCEPTIONS(i).ERROR_CODE));
     END LOOP;
  END;
END;
/
SET ECHO ON
SELECT COUNT(*)
FROM   exception_test;
SET ECHO OFF
Notice that in addition to the SAVE EXCEPTIONS clause being removed, the no_save_exceptions.sql script now traps a different error number.  The output from this script is listed below.
SQL> @no_save_exceptions.sql
Number of failures: 1
Error: 1 Array Index: 50 Message: ORA-01400: cannot insert NULL into
("TIM_HALL"."EXCEPTION_TEST"."ID")
PL/SQL procedure successfully completed.
SQL> SELECT COUNT(*)
  2  FROM   exception_test;
  COUNT(*)
----------
        49
1 row selected.
SQL> SET ECHO OFF
As expected there is only a single error in the SQL%BULK_EXCEPTIONS collection, and there are only 49 records in the test table as the operation has rolled back to the preceding implicit savepoint.


Wednesday, February 5, 2014

Back Button Auto Focus

Source
link

  1. Verify that your camera has an AF-On button.  If not, you’ll need to set up the AE/AF-lock button in the custom menus to use it as the AF-On button.  In the Nikon D90, this is custom setting f4.
  2. Set the camera’s AF servo mode to Continuous (AF-C).  This is done through the switch next to your lens mount, or via a custom menu setting. D90 users: hold down the AF button on the top of your camera, and turn the Main Command Dial until AF-C is displayed in the top LCD panel.
  3. In the camera menus, go to submenu “a” (Autofocus)
  4. Set custom setting a1 (Continuous Release Mode) to Release Priority (in the D90, this is already set for you when you choose continuous servo AF mode)
  5. Find the custom setting for AF Activation (a5 on the D3s) and set it to AF-On Only. This step is not necessary for the D90 and other cameras, as it is already set up by custom setting f4.
Now you’re all set up and ready to go.

HOW TO USE THE AF-ON TECHNIQUE IN THE FIELD

To emulate single-servo mode (focus/recompose/shoot)
  1. Place the active AF point on your subject
  2. Press the AF-On button to acquire focus
  3. Release the AF-On button to lock focus
  4. Recompose and shoot
To focus continuously on a moving subject
  1. Place the active AF point on the subject
  2. Press the AF-On button
  3. Keep the AF-On button pressed to track focus while simultaneously pressing the shutter release
  4. Remember to initiate the VR system (if your lens supports it) by half-pressing the shutter button prior to releasing the shutter.  Remember, VR takes about a half-second to stabilize, so you’ll want to anticipate your subject.
Now that you understand how to use the technique, you’ll want to spend some time practicing.  It usually takes about a day of shooting in the field to get used to the new technique.  Once you know how to use it, the AF-On only method of focusing will help you get more “keeper” shots.

Tuesday, January 28, 2014

OM Flow with Tables

Order Management Tables.

Entered
oe_order_headers_all 1 record created in header table
oe_order_lines_all Lines for particular records
oe_price_adjustments When discount gets applied
oe_order_price_attribs If line has price attributes then populated
oe_order_holds_all If any hold applied for order like credit check etc.

Booked

oe_order_headers_all Booked_flag=Y Order booked.
wsh_delivery_details Released_status Ready to release

Pick Released

wsh_delivery_details Released_status=Y Released to Warehouse (Line has been released to Inventory for processing)
wsh_picking_batches After batch is created for pick release.
mtl_reservations This is only soft reservations. No physical movement of stock

Full Transaction

mtl_material_transactions No records in mtl_material_transactions
mtl_txn_request_headers
mtl_txn_request_lines

wsh_delivery_details Released to warehouse.
wsh_new_deliveries if Auto-Create is Yes then data populated.
wsh_delivery_assignments deliveries get assigned

Pick Confirmed

wsh_delivery_details Released_status=Y Hard Reservations. Picked the stock. Physical movement of stock

Ship Confirmed

wsh_delivery_details Released_status=C Y To C:Shipped ;Delivery Note get printed Delivery assigned to trip stopquantity will be decreased from staged
mtl_material_transactions On the ship confirm form, check Ship all box
wsh_new_deliveries If Defer Interface is checked I.e its deferred then OM & inventory not updated. If Defer Interface is not checked.: Shipped

oe_order_lines_all Shipped_quantity get populated.
wsh_delivery_legs 1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
oe_order_headers_all If all the lines get shipped then only flag N

Autoinvoice

wsh_delivery_details Released_status=I Need to run workflow background process.
ra_interface_lines_all Data will be populated after wkfw process.
ra_customer_trx_all After running Autoinvoice Master Program for
ra_customer_trx_lines_all specific batch transaction tables get populated

Price Details

qp_list_headers_b To Get Item Price Details.
qp_list_lines
Items On Hand Qty
mtl_onhand_quantities TO check On Hand Qty Items.

Payment Terms

ra_terms Payment terms

AutoMatic Numbering System

ar_system_parametes_all you can chk Automactic Numbering is enabled/disabled.

Customer Information

hz_parties Get Customer information include name,contacts,Address and Phone
hz_party_sites
hz_locations
hz_cust_accounts
hz_cust_account_sites_all
hz_cust_site_uses_all
ra_customers

Document Sequence

fnd_document_sequences Document Sequence Numbers
fnd_doc_sequence_categories
fnd_doc_sequence_assignments
Default rules for Price List
oe_def_attr_def_rules Price List Default Rules
oe_def_attr_condns
ak_object_attributes
End User Details
csi_t_party_details To capture End user Details

Sales Credit Sales Credit Information(How much credit can get)

oe_sales_credits

Attaching Documents

fnd_attached_documents Attched Documents and Text information
fnd_documents_tl
fnd_documents_short_text

Blanket Sales Order

oe_blanket_headers_all Blanket Sales Order Information.
oe_blanket_lines_all

Processing Constraints

oe_pc_assignments Sales order Shipment schedule Processing Constratins
oe_pc_exclusions
Sales Order Holds
oe_hold_definitions Order Hold and Managing Details.
oe_hold_authorizations
oe_hold_sources_all
oe_order_holds_all

Hold Relaese

oe_hold_releases_all Hold released Sales Order.

Credit Chk Details

oe_credit_check_rules To get the Credit Check Againt Customer.

Cancel Orders

oe_order_lines_all Cancel Order Details.


Source