transaction_source_id in MMT

Source


See the correnpondances below:
a)TRANSACTION_SOURCE_ID: Job or Schedule WIP_ENTITIES.WIP_ENTITY_ID
TRANSACTION_SOURCE_TYPE_ID = 5

b) TRANSACTION_SOURCE_ID: Sales Order MTL_SALES_ORDERS.SALES_ORDER_ID
TRANSACTION_SOURCE_TYPE_ID = 2, 8, 12, 13

c) TRANSACTION_SOURCE_ID: Account Alias MTL_GENERIC_DISPOSITIONS.DISPOSITION_ID
TRANSACTION_SOURCE_TYPE_ID = 6

d) TRANSACTION_SOURCE_ID: Purchase Order PO_HEADERS_ALL.PO_HEADER_ID
TRANSACTION_SOURCE_TYPE_ID = 1

e) TRANSACTION_SOURCE_ID: Account GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
TRANSACTION_SOURCE_TYPE_ID = all others

A useful select to find the specific source number and link it to TRANSACTION_SOURCE_ID is:

SELECT MMTT.TRANSACTION_SOURCE_ID,
CASE WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 1 THEN (SELECT 'RSH_NUMBER: ' || RCV.SHIPMENT_NUM 
FROM RCV_SHIPMENT_HEADERS RCV,
RCV_TRANSACTIONS RCVT
WHERE RCV.SHIPMENT_HEADER_ID = RCVT.SHIPMENT_HEADER_ID
AND RCVT.TRANSACTION_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 2 THEN (SELECT 'SO_NUMBER: ' || SEGMENT1
FROM MTL_SALES_ORDERS
WHERE SALES_ORDER_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 4 THEN (SELECT 'MO_NUMBER: ' || REQUEST_NUMBER
FROM MTL_TXN_REQUEST_HEADERS
WHERE REQUEST_NUMBER = TO_CHAR(MMTT.TRANSACTION_SOURCE_ID))
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 5 THEN (SELECT 'WIP_NUMBER: ' || WIP_ENTITY_NAME
FROM WIP_ENTITIES
WHERE WIP_ENTITY_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 7 THEN (SELECT 'INT_REQ_NUMBER: ' || RCV.SHIPMENT_NUM 
FROM RCV_SHIPMENT_HEADERS RCV,
RCV_TRANSACTIONS RCVT
WHERE RCV.SHIPMENT_HEADER_ID = RCVT.SHIPMENT_HEADER_ID
AND RCVT.TRANSACTION_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 8 THEN (SELECT 'INT_SO_NUMBER: ' || SEGMENT1
FROM MTL_SALES_ORDERS
WHERE SALES_ORDER_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 10 THEN (SELECT 'PHY_NAME: ' || PHYSICAL_INVENTORY_NAME
FROM MTL_PHYSICAL_INVENTORIES
WHERE PHYSICAL_INVENTORY_ID = MMTT.TRANSACTION_SOURCE_ID)
WHEN MMTT.TRANSACTION_SOURCE_TYPE_ID = 13 THEN (SELECT 'WIP_NUMBER: ' || WIP_ENTITY_NAME
FROM WIP_ENTITIES
WHERE WIP_ENTITY_ID = MMTT.TRANSACTION_SOURCE_ID)
ELSE 'NULL' END SRC_NUMBER 
FROM MTL_MATERIAL_TRANSACTIONS_TEMP MMTT.

Term insurance policy riders

Choosing Term Insurance -- Good

Insurance Companies Claim/Settlement Ratio

1. Accidental Death Riders- This means you will get additional life cover but only if you get death from accident

2. Critical Illness Rider- This will help you to get additional life cover if you die due to the illness mentioned in the policy while buying it

3. Disability Rider- This rider covers you for disability and pays you life cover in some predefined installments in the case where you become permanent disable

4. Waiver of Premium- In case you become permanently disable due to some accident, you would be waived off for the future premium payments while your term insurance policy will remain in continuation

Finally while choosing the term insurance plan, one can recommend choosing HDFC Life Insurance which has high claim settlement ratio though it has high premium, this option may be one of the best term insurance policies in India.

Source : life-insurance-riders

What are Riders in Term Insurance?




Riders are the extra benefits that can be purchased and covered for under the life insurance policy. Apart from the basic Life insurance cover, you can choose to add some extra benefits to the life insurance cover, but you will have to pay extra premium to get such add-on benefits. The basic premiums will then increase. Note that the base policy features are always there and you get the base Sum Assured in case of death. Addition of these riders has nothing to do with the original rules of the policy. Let us see all the riders one by one.

1. Accidental Death Rider

In this rider, you get additional sum assured if the death occurs due to an accident. The biggest myth which investors have is that they will get the money if death is due to accident only if this rider is added, else not. This is not true. If you don’t take this rider, still the base Sum assured will be paid to you. This rider is only for the extra sum assured in case of death due to accident at additional cost, nothing else. So if you take a policy of 50 lacs sum assured with accidental rider of 25 lacs. You will get 50 lacs in case of death other than accident and 75 lacs in case of death in accident. A lot of policies cover you from disabilities which arise out of accidents. See Accidental Insurance Policies

2. Permanent & Partial Disability

This rider is helpful in case you are disabled permanently or temporarily due to accident. In that case most of the policies pay periodically for next 5-10 yrs a certain percentage of Sum Assured. For example, 10% of Sum Assured per year for next 10 yrs. This way this rider acts like an income generation insurance most of the times. However note that the rider is helpful only incase the disability happens due to accident only. Read the policy document of the company for exact wordings. Most of the times, this rider is combined with Accident Death rider.

3. Critical Illness

This rider gives you a lump sum amount if you are diagnosed with an illness which is pre-specified and is mentioned in the policy. Generally all the major illnesses are covered in Critical Illness cover. Some of the examples of critical illness mentioned are Heart Attack, Cancer, Stroke, Coronary artery by-pass graft surgery (CABG), Kidney failure and Paralysis for example. After the critical illness is detected, the policy might continue or terminate as per the policy document. At times, the policy coverage reduces by the amount paid to you. So better read the policy document to know exactly what will happen in this rider.

4. Waiver of Premium

This rider makes sure that in case you are not able to pay future premium due to disability or income loss, the future premiums are waived off but your policy is still in force like always. This is in a way insurance of the premium payment till your policy expiry date. In case this rider is not present and you are disabled and not able to pay the premiums, then the policy will expire and you will not get any benefit later when you die because due to non-payment of premium the policy expires and the cover stops.

5. Income Benefit Rider

This rider is present in some policies and it’s mainly for the income generation after the death of the policyholder. If this rider is present, the policy holder’s family will get additional income per year for 5-10 yrs along with regular Sum Assured. For example, 10% of Sum Assured for next 10 yrs will be received by the policy holder’s family.

Riders come with cost and exclusions



Note that riders come with cost, so just because they are present in the policy as add-ons, don’t jump and include every kind of rider possible. Ask yourself why you need a rider and if there is really a need for it. Read about the rider rules in details and read what is not included in that rider. Also compare the cost of riders from different companies to take a better decision.

Troubling Messages in WorkFlow

Notifications are not being sent by the notification mailer 

Bija Mantras

Sounds Of The Chakras

Within each human being lies the power to affect change through the power of a chant, the spoken words, or even a gentle whisper. The body's chakras or energy centers, so closely intertwined with their corresponding regions of the body, can be represented in sound, which parallels the energy pattern of the chakras and is symbolic of their essences. These unique sounds are the bija, or seed, mantras. The mantras are the one-syllable seed sounds that, when said aloud, activate the energy of the chakras in order to purify and balance the mind and body. When you speak the bija mantras, you resonate with the energy of the associated chakra, helping you focus upon your own instinctive awareness of your body and its needs.




OM is the most renowned and expansive of the bija mantras. It is the mantra of assent and the form of creation, causing energy to surge upward and outward.



KRIM (pronounced as 'kreem') stimulates and transforms the lower chakras, awakening and purifying the body.



SHRIM (pronounced 'shreem') is associated with the head and third eye and, while promoting health, can be used to flood the senses with delight and beauty.



HRIM (pronounced 'hreem') holds creativity and healing powers. Speaking it has the power to awaken and purify the heart.



HUM (pronounced 'hoom') destroys negativity and inspires vitality throughout the body.



In traditional Hatha Yoga, the seven cleansing bija mantras associated with the chakras are:



LAM for the earth chakra (1)

VAM for the water chakra (2)

RAM for the fire chakra (3)

YAM for the heart chakra (4)

HAM for the throat chakra (5)

AUM for the third eye (6)

AH for the crown chakra (7)



But the seed mantras, which are vessels of a self-generating power, are by no means truly rigid. The meaning of each seed mantra can be subtly changed through their intonation and the intention of those who speak them. When you chant the bija mantras, either one at a time or in sequences most often beginning with OM, your mind will be gradually become attuned to the mantras' finer frequencies until the source energy is reached and the mantra becomes the seed of spiritual energy of the chakras

Hari Om Tat Sat

Hari Om Tat Sat   ‘Hari Om Tat Sat’ is a very ancient mantra from the Vedas. ‘Hari Om’ is one mantra and ‘Om Tat Sat’ another. I have joined the two in ‘Hari Om Tat Sat’. ‘Hari’ represents the manifest universe and life. ‘Om’ represents the unmanifest and absolute reality. By the word ‘reality’, I mean total existence. You may even use the word God. Reality, existence, God, Brahman, the absolute are all synonymous terms pointing to one being, but they do not really define it.



This reality has two stages. One is the absolute, the other is manifest. This gross universe, the millions of suns, moons and stars, space, that which is beyond it and beyond this little earth, as far as we can go, are all manifestations of that reality, not a creation of reality. There is a difference between the process of creation and manifestation. You take cotton and make yarn from it, and then a shirt. The cotton has become the shirt, it has not created the shirt. The cotton has transformed itself into a shirt. In the same way, there is a great invisible force. Nobody can see it and nobody has seen it, except for a few people who we call avataras.



The manifest reality, this world, is represented by the mantra ‘Hari’. ‘Om’ is the unmanifest reality, the unseen, invisible, uncreated aspect of the absolute. So, ‘Hari Om Tat Sat’ means ‘That is Truth’. That which I see with my eyes and that which is beyond my eyes are both the same, not different. The creator and the creation are not two. The creator has not created creation, but has manifested or transformed himself into creation.



All these truths are represented in the mantra ‘Hari Om Tat Sat’. When I say ‘Hari Om Tat Sat’, it reminds me that the seen and the unseen, are both one.

LOGGING in PO

Debug logging can be enabled at the Document Manager Level to show activities done during processing for deeper analysis. This is done using the following steps;

1. Set the following profile options at the Oracle Purchasing Application level.

Set "PO: Set Debug Workflow ON" to "Yes"

Set "PO: Set Debug Concurrent ON " to "Yes"

2. Set the number of Document Manager processes to 1

3. Clear the debug table by deleting the contents of po_wf_debug table

4. Bounce the Document Manager process.

5. Reproduce the issue.

6. Query the po_wf_debug table so find the log lines written.

7. Revert the profile option settings:

8. Bounce the Document Approval Manager to update the setting changes.

Purchasing approval processing

TROUBLESHOOTING

The following section provides some details on diagnosing some common issues in the Purchasing approval processing

1) Document Approval Logic:

Issue 1

Document remains in Incomplete status after Approval



Cause 1A

The creator of the document is not part of a valid approval hierarchy, and does not have the limits to make the approval. The user needs to be associated to a valid Approval Hierarchy that address the approval limits for the specific document type. If employee / supervisor relation is being used for the document approval routing, then the needed assignments and association for each approval level will need to be done through the Enter Person form for each sequential employee/supervisor. For details on assigning employees, refer to Oracle Purchasing User’s Guide Release 11i (Part No. A82913–06) in 11.5.10 or Oracle Purchasing User's Guide Release 12 (Part No. B28669-01)



Cause 1B

The creator is part of a valid hierarchy, but there is not a level within the hierarchy that covers the elements on the document. The main culprit for this is the Change Account. Verify that for each of the limits under each level, that the number of digits for each segment in the account ranges matches that of the Charge Account. If the segment count appears to be correct, perform a quick test, and move the top of the account for the last level to be ‘Z’ for each digit. (Ex: ZZ.ZZZ.ZZ.ZZZZ.ZZZZ) If the resubmit of the approval now moves through without issue, then it is known that the cause was the Account Range, and new limits just need to be set for the each level.

Issue 2


Document rolls-up to the next approval level, when it should be approved by the owner.

Cause 2A

The assigned approval limits for the owner/creator are not broad or high enough to allow for document approval at the owner level. Review the approval limits and conditions assigned to the owner, and match each against a document that rolled-up to the next level.

Cause 2B

Even though the owner/creator has the correct approval limits for the document approval, the “Owner Can Approve” option under the document type setup has not been set to “Y”. For an owner/creator to be able to approve their own documents, this setting must be defined as “Y”.

Issue 3

Unable to open Requisitions or Purchase Orders from the document summary, for approval.

Cause 3A

The document is in either In Process or Pre-Approved status. A majority of the time, there is an open notification against either the Requisition or Purchase Order. The following query set can be used to determine the current user the notification action is waiting for:

Requisition:


select reqh.segment1 req, wfn.status notify_status, wias.notification_id notify_id,
wfn.to_user name, reqh.org_id org from wf_item_activity_statuses wias, wf_notifications wfn, po_requisition_headers_all reqh
where wias.notification_id is not null and wias.notification_id = wfn.group_id
and wfn.status = 'OPEN' and wias.item_type = 'REQAPPRV'
and wias.item_key = reqh.wf_item_key and reqh.authorization_status = ‘&Req_Number’ order by 5,1,3;

Purchase Order:

select poh.segment1 po, wfn.status notify_status, wias.notification_id notify_id,
wfn.to_user name, poh.org_id org from wf_item_activity_statuses wias,
wf_notifications wfn, po_headers_all poh where wias.notification_id is not null
and wias.notification_id = wfn.group_id and wfn.status = 'OPEN'
and wias.item_type = 'POAPPRV' and wias.item_key = poh.wf_item_key and poh.segment1 = ‘&PO_Number’ order by 4,5,1,3;

Cause 3B

The Purchase Order is in In Process or Pre-Approved status, but does not have any Workflow data. The most common cause for this is that there is an Open Change request against the Purchase Order/Requisition combination. Because the Purge Obsolete Workflow Process may have been run against the document between the last time the Approval took place and the Change Request was raised, the WF data would be missing. The correct action in this case is to have the Buyer, which the Change Request is waiting on, reply to the notification to either except or reject the change. The following query can be used to review the ties between the Purchase Order, Requisition and Change Request.

Purchase Order:


select ref_po_num PO_Num, ref_po_rel_num Rel_Num, document_num Req_Num,
change_request_id CR_Id, change_request_group_id CR_Grp_ID,
last_update_date, document_line_number Doc_Line_Num, action_type,
request_reason, request_status status from po_change_requests where ref_po_header_id =
(select po_header_id from po_headers_all where segment1 = '&PO_NUMBER' and org_id = '&ORG_ID')
and document_type = 'REQ' order by last_update_date

Requisition:

select ref_po_num PO_Num, ref_po_rel_num Rel_Num, document_num Req_Num,
change_request_id CR_Id, change_request_group_id CR_Grp_ID,
last_update_date, document_line_number Doc_Line_Num, action_type,
request_reason, request_status status from po_change_requests where document_header_id =
(select requisition_header_id from po_requisition_headers_all where segment1 = '&Req_NUMBER'
and org_id = '&ORG_ID') and document_type = 'REQ' order by last_update_date