eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PON_TCA_MERGE_PVT dependencies on PON_BID_HEADERS

Line 1791: -- merge for Sourcing PON_BID_HEADERS entity.

1787: -- Pre-reqs : Responses with the given surrog_bid_created_contact_id
1788: -- (p_From_FK_id) must exists in the database
1789: --
1790: -- Function : This procedure will be attached to the SURROG_BID_CREATED_CONTACT_ID
1791: -- merge for Sourcing PON_BID_HEADERS entity.
1792: --
1793: -- It will veto Party Merge if -
1794: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1795: --

Line 1796: -- This will merge the all the PON_BID_HEADERS records

1792: --
1793: -- It will veto Party Merge if -
1794: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1795: --
1796: -- This will merge the all the PON_BID_HEADERS records
1797: -- having SURROG_BID_CREATED_CONTACT_ID equals to p_From_FK_id
1798: -- to party id having value (p_To_FK_id)
1799: --
1800: -- Parameters:

Line 1881: -- PON_BID_HEADERS.SURROG_BID_CREATED_CONTACT_ID

1877:
1878: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
1879: --
1880: -- This can not happen in any normal scenario as
1881: -- PON_BID_HEADERS.SURROG_BID_CREATED_CONTACT_ID
1882: -- can never contain a seller user id. Thus, raising a veto though
1883: -- it will possibly never be called
1884: --
1885: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 1899: UPDATE PON_BID_HEADERS

1895: --
1896: -- there is no chance of unique key constraint violation
1897: -- due to the following updates
1898: --
1899: UPDATE PON_BID_HEADERS
1900: SET LAST_UPDATE_DATE = SYSDATE,
1901: LAST_UPDATED_BY = -1,
1902: SURROG_BID_CREATED_CONTACT_ID = p_To_FK_id
1903: WHERE SURROG_BID_CREATED_CONTACT_ID = p_From_FK_id;

Line 1905: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SURROG_BID_CREATED_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

1901: LAST_UPDATED_BY = -1,
1902: SURROG_BID_CREATED_CONTACT_ID = p_To_FK_id
1903: WHERE SURROG_BID_CREATED_CONTACT_ID = p_From_FK_id;
1904:
1905: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SURROG_BID_CREATED_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
1906:
1907: --
1908: -- We will be updating the user_id column of pon_neg_team_members table
1909: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 1952: -- merge for Sourcing PON_BID_HEADERS entity.

1948: -- Pre-reqs : Responses with the given score_override_tp_contact_id
1949: -- (p_From_FK_id) must exists in the database
1950: --
1951: -- Function : This procedure will be attached to the SCORE_OVERRIDE_TP_CONTACT_ID
1952: -- merge for Sourcing PON_BID_HEADERS entity.
1953: --
1954: -- It will veto Party Merge if -
1955: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1956: --

Line 1957: -- This will merge the all the PON_BID_HEADERS records

1953: --
1954: -- It will veto Party Merge if -
1955: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1956: --
1957: -- This will merge the all the PON_BID_HEADERS records
1958: -- having SCORE_OVERRIDE_TP_CONTACT_ID equals to p_From_FK_id
1959: -- to party id having value (p_To_FK_id)
1960: --
1961: -- Parameters:

Line 2043: -- PON_BID_HEADERS.SCORE_OVERRIDE_TP_CONTACT_ID

2039: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
2040:
2041: --
2042: -- This can not happen in any normal scenario as
2043: -- PON_BID_HEADERS.SCORE_OVERRIDE_TP_CONTACT_ID
2044: -- can never contain a seller user id. Thus, raising a veto though
2045: -- it will possibly never be called
2046: --
2047: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 2063: UPDATE PON_BID_HEADERS

2059: --
2060: -- there is no chance of unique key constraint violation
2061: -- due to the following updates
2062: --
2063: UPDATE PON_BID_HEADERS
2064: SET LAST_UPDATE_DATE = SYSDATE,
2065: LAST_UPDATED_BY = -1,
2066: SCORE_OVERRIDE_TP_CONTACT_ID = p_To_FK_id
2067: WHERE SCORE_OVERRIDE_TP_CONTACT_ID = p_From_FK_id;

Line 2069: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SCORE_OVERRIDE_TP_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

2065: LAST_UPDATED_BY = -1,
2066: SCORE_OVERRIDE_TP_CONTACT_ID = p_To_FK_id
2067: WHERE SCORE_OVERRIDE_TP_CONTACT_ID = p_From_FK_id;
2068:
2069: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SCORE_OVERRIDE_TP_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
2070:
2071: --
2072: -- We will be updating the user_id column of pon_neg_team_members table
2073: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 2115: -- merge for Sourcing PON_BID_HEADERS entity.

2111: -- Pre-reqs : Responses with the given shortlist_tpc_id
2112: -- (p_From_FK_id) must exists in the database
2113: --
2114: -- Function : This procedure will be attached to the SHORTLIST_TPC_ID
2115: -- merge for Sourcing PON_BID_HEADERS entity.
2116: --
2117: -- It will veto Party Merge if -
2118: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
2119: --

Line 2120: -- This will merge the all the PON_BID_HEADERS records

2116: --
2117: -- It will veto Party Merge if -
2118: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
2119: --
2120: -- This will merge the all the PON_BID_HEADERS records
2121: -- having SHORTLIST_TPC_ID equals to p_From_FK_id
2122: -- to party id having value (p_To_FK_id)
2123: --
2124: -- Parameters:

Line 2205: -- PON_BID_HEADERS.SHORTLIST_TPC_ID

2201:
2202: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
2203: --
2204: -- This can not happen in any normal scenario as
2205: -- PON_BID_HEADERS.SHORTLIST_TPC_ID
2206: -- can never contain a seller user id. Thus, raising a veto though
2207: -- it will possibly never be called
2208: --
2209: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 2223: UPDATE PON_BID_HEADERS

2219: --
2220: -- there is no chance of unique key constraint violation
2221: -- due to the following updates
2222: --
2223: UPDATE PON_BID_HEADERS
2224: SET LAST_UPDATE_DATE = SYSDATE,
2225: LAST_UPDATED_BY = -1,
2226: SHORTLIST_TPC_ID = p_To_FK_id
2227: WHERE SHORTLIST_TPC_ID = p_From_FK_id;

Line 2229: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SHORTLIST_TPC_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

2225: LAST_UPDATED_BY = -1,
2226: SHORTLIST_TPC_ID = p_To_FK_id
2227: WHERE SHORTLIST_TPC_ID = p_From_FK_id;
2228:
2229: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SHORTLIST_TPC_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
2230:
2231: --
2232: -- We will be updating the user_id column of pon_neg_team_members table
2233: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 3719: -- merge for Sourcing PON_BID_HEADERS entity.

3715: -- Pre-reqs : Responses with the given draft_unlocked_by_contact_id
3716: -- (p_From_FK_id) must exists in the database
3717: --
3718: -- Function : This procedure will be attached to the DRAFT_UNLOCKED_BY_CONTACT_ID
3719: -- merge for Sourcing PON_BID_HEADERS entity.
3720: --
3721: -- It will veto Party Merge if -
3722: -- p_From_FK_id and p_To_FK_id both are not Seller or Buyer user party
3723: --

Line 3724: -- This will merge the all the PON_BID_HEADERS records

3720: --
3721: -- It will veto Party Merge if -
3722: -- p_From_FK_id and p_To_FK_id both are not Seller or Buyer user party
3723: --
3724: -- This will merge the all the PON_BID_HEADERS records
3725: -- having DRAFT_UNLOCKED_BY_CONTACT_ID equals to p_From_FK_id
3726: -- to party id having value (p_To_FK_id)
3727: --
3728: -- Parameters:

Line 3809: -- PON_BID_HEADERS.DRAFT_UNLOCKED_BY_CONTACT_ID

3805:
3806: fnd_file.put_line (fnd_file.log, '20 : Incompatible Merge - Error');
3807: --
3808: -- This can not happen in any normal scenario as
3809: -- PON_BID_HEADERS.DRAFT_UNLOCKED_BY_CONTACT_ID
3810: -- can never contain a buyer user id which is merged to a seller user.
3811: -- Thus, raising a veto though
3812: -- it will possibly never be called
3813: --

Line 3825: UPDATE PON_BID_HEADERS

3821: --
3822: -- there is no chance of unique key constraint violation
3823: -- due to the following updates
3824: --
3825: UPDATE PON_BID_HEADERS
3826: SET LAST_UPDATE_DATE = SYSDATE,
3827: LAST_UPDATED_BY = -1,
3828: DRAFT_UNLOCKED_BY_CONTACT_ID = p_To_FK_id
3829: WHERE DRAFT_UNLOCKED_BY_CONTACT_ID = p_From_FK_id;

Line 3831: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated DRAFT_UNLOCKED_BY_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

3827: LAST_UPDATED_BY = -1,
3828: DRAFT_UNLOCKED_BY_CONTACT_ID = p_To_FK_id
3829: WHERE DRAFT_UNLOCKED_BY_CONTACT_ID = p_From_FK_id;
3830:
3831: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated DRAFT_UNLOCKED_BY_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
3832:
3833: ELSIF (l_merge_scenario = G_IRRELEVANT) THEN
3834: --
3835: -- Nothing to do

Line 3867: -- merge for Sourcing PON_BID_HEADERS entity.

3863: -- Pre-reqs : Responses with the given draft_locked_by_contact_id
3864: -- (p_From_FK_id) must exists in the database
3865: --
3866: -- Function : This procedure will be attached to the DRAFT_LOCKED_BY_CONTACT_ID
3867: -- merge for Sourcing PON_BID_HEADERS entity.
3868: --
3869: -- It will veto Party Merge if -
3870: -- p_From_FK_id and p_To_FK_id both are not Seller or Buyer user party
3871: --

Line 3872: -- This will merge the all the PON_BID_HEADERS records

3868: --
3869: -- It will veto Party Merge if -
3870: -- p_From_FK_id and p_To_FK_id both are not Seller or Buyer user party
3871: --
3872: -- This will merge the all the PON_BID_HEADERS records
3873: -- having DRAFT_LOCKED_BY_CONTACT_ID equals to p_From_FK_id
3874: -- to party id having value (p_To_FK_id)
3875: --
3876: -- Parameters:

Line 3957: -- PON_BID_HEADERS.DRAFT_LOCKED_BY_CONTACT_ID

3953:
3954: fnd_file.put_line (fnd_file.log, '20 : Incompatible Merge - Error');
3955: --
3956: -- This can not happen in any normal scenario as
3957: -- PON_BID_HEADERS.DRAFT_LOCKED_BY_CONTACT_ID
3958: -- can never contain a buyer user id which is merged to a seller user id.
3959: -- Thus, raising a veto though
3960: -- it will possibly never be called
3961: --

Line 3973: UPDATE PON_BID_HEADERS

3969: --
3970: -- there is no chance of unique key constraint violation
3971: -- due to the following updates
3972: --
3973: UPDATE PON_BID_HEADERS
3974: SET LAST_UPDATE_DATE = SYSDATE,
3975: LAST_UPDATED_BY = -1,
3976: DRAFT_LOCKED_BY_CONTACT_ID = p_To_FK_id
3977: WHERE DRAFT_LOCKED_BY_CONTACT_ID = p_From_FK_id;

Line 3979: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated DRAFT_LOCKED_BY_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

3975: LAST_UPDATED_BY = -1,
3976: DRAFT_LOCKED_BY_CONTACT_ID = p_To_FK_id
3977: WHERE DRAFT_LOCKED_BY_CONTACT_ID = p_From_FK_id;
3978:
3979: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated DRAFT_LOCKED_BY_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
3980:
3981: ELSIF (l_merge_scenario = G_IRRELEVANT) THEN
3982: --
3983: -- Nothing to do

Line 4014: -- merge for Sourcing PON_BID_HEADERS entity.

4010: -- Pre-reqs : Responses with the given trading_partner_contact_id
4011: -- (p_From_FK_id) must exists in the database
4012: --
4013: -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
4014: -- merge for Sourcing PON_BID_HEADERS entity.
4015: --
4016: -- It will veto Party Merge if -
4017: -- p_From_FK_id and p_To_FK_id both are not Seller user party
4018: --

Line 4019: -- This will merge the all the PON_BID_HEADERS records

4015: --
4016: -- It will veto Party Merge if -
4017: -- p_From_FK_id and p_To_FK_id both are not Seller user party
4018: --
4019: -- This will merge the all the PON_BID_HEADERS records
4020: -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
4021: -- to party id having value (p_To_FK_id)
4022: --
4023: -- Parameters:

Line 4105: -- PON_BID_HEADERS.TRADING_PARTNER_CONTACT_ID

4101:
4102: fnd_file.put_line (fnd_file.log, '20 : Buyer or Incompatible Merge - Error');
4103: --
4104: -- This can not happen in any normal scenario as
4105: -- PON_BID_HEADERS.TRADING_PARTNER_CONTACT_ID
4106: -- can never contain a buyer user id. Thus, raising a veto though
4107: -- it will possibly never be called
4108: --
4109: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 4132: UPDATE PON_BID_HEADERS pb

4128: -- two active bids from the same supplier but different trading
4129: -- partner contact id
4130: --
4131:
4132: UPDATE PON_BID_HEADERS pb
4133: SET pb.LAST_UPDATE_DATE = SYSDATE,
4134: pb.LAST_UPDATED_BY = -1,
4135: pb.TRADING_PARTNER_CONTACT_ID = p_To_FK_id,
4136: pb.TRADING_PARTNER_CONTACT_NAME = l_user_name

Line 4139: FROM PON_BID_HEADERS pb1

4135: pb.TRADING_PARTNER_CONTACT_ID = p_To_FK_id,
4136: pb.TRADING_PARTNER_CONTACT_NAME = l_user_name
4137: WHERE pb.TRADING_PARTNER_CONTACT_ID = p_From_FK_id
4138: AND NOT EXISTS (SELECT 'DUPLICATE'
4139: FROM PON_BID_HEADERS pb1
4140: WHERE pb1.AUCTION_HEADER_ID = pb.AUCTION_HEADER_ID
4141: AND pb1.TRADING_PARTNER_ID <> pb.TRADING_PARTNER_ID
4142: AND pb1.TRADING_PARTNER_CONTACT_ID = p_To_FK_id
4143: AND pb1.BID_STATUS = 'ACTIVE');

Line 4146: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated TRADING_PARTNER_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');

4142: AND pb1.TRADING_PARTNER_CONTACT_ID = p_To_FK_id
4143: AND pb1.BID_STATUS = 'ACTIVE');
4144:
4145:
4146: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated TRADING_PARTNER_CONTACT_IDs in PON_BID_HEADERS: '||sql%rowcount||' rows');
4147:
4148: ELSIF (l_merge_scenario = G_IRRELEVANT) THEN
4149: --
4150: -- Nothing to do