Finally Closed setup control in Purchasing

Hi All,
Is there a way to disable users from "FINALLY CLOSING" PO's. If so what is the procedure to do that? Is that something done in workfloww????
Any Ideas?
Thanks,
Prathima

For some reason I couldn't edit my first message which I sent out accidentally before it was complete.
Here's the full version:
Greetings,
I use a stepper motor with timing belt to enable linear motion in an axis. I can get real time absolute linear position information with the help of linear sensors and convert them to actual step data using math operations. I was trying to find a way to feed this data back to the VI that moves the motor and create a closed control loop using LabView (not MAX). Overshoot and multiple pull in's are not a problem as long as the final position is correct (or within a certain tolerance). I was wondering if it was possible to feed the actual step data (which I received and calculated from linear sensors) to Movement VI's in LabView as "desired position" value? Is this possible? If not, does someone have another suggestion?
Thank you.
My setup is as follows: PCIe 6321 and BNC 2110 for position measurement
PCI7332 and UMI 7772 for motor control

Similar Messages

Purchase order finally closed

Hi Team ,
Purchase order header status is " Finally closed " , we have one line and delivery is pending . Now is there any way to receive the item , because we can not open the finally closed PO .
Thanks
Kiran

We want to inactivate Inventory Org but , PO receiving is reflecting in All Inventories value report .
We can not deliver PO for finally closed PO . As a workaroung we can do Misc Transcaction , but report will show pending receiving .
Thanks
Kiran

Purchase Order is Finally Closed

Hi to All,
Question: If a PO is finally closed. And the receiving department incorreclty received the items. Is there a way to fix the receiving qty after the PO has been finally closed.
thanks in advance for help on this matter.

Refer to this thread. Bring it back to approved status and perform necessary transactions.
How to Change a PO from Finally Closed back to Approved
Thanks
Nagamohan

Disable Finally Closed option on PO

Hi,
Is there a way to disable the Finally Closed option on the PO?
Its not possible with Form personalization because the entire control field gets disabled.
Any ideas?
Thanks,
Ashwathy John

i will try to accomplish through custom.dll
Pl also suggest on this
We make Approval Group based on item category for PR or PO approval. The question is , i want to get approval group based on item or its category. Just pass item id and get which approval group is going to approval this item.
i got po_control_rules table it just contains categories range in description form, but didn't get any proper help.
Pl suggest solution
Regards,

Period End closing in controlling module.

Hi Gurus,
In our project, we have implemented FI, CO , MM, SD, PP, PM, and HR modules with payrolls. Our project has gone live this month(05.02.2007).
Can anybody explain what are the steps to be taken for period closing in controlling.
Some Production orders which are in process do not have standard cost estimates, what is the impact in WIP Calculation.
Please also give info on how to transfer the Personnel Cost from HR Cost Centers to deferent production orders.
Thanks in Advance
Ganesh

here is the list for FI/CO year end closing check list:
1 Execute Report for InterCompany Activity & Journal Entries
2 Open posting period for next yr
3 Run Business Area's Assignment report.
4 Review list of recurring journal entries
5 Execute Recurring Entries for A/R, A/P, G/L
6 Process Parked A/R, A/P, G/L accounting documents
7 Final Cutoff for the Maintenance of Fixed Asset- Add Transfer and Retire
8 Run Depreciation in Test Run and post
9 Verify Display Log for Depreciation Test Run
10 Capitalize AUC Assets if needed
11 Enter Payroll Data to SAP
12 Verify Depreciation Balances with GL balances
13 Post Depreciation
14 Execute Asset History Report, and retire assets if needed
15 Adjust specific depreciation areas if necessary
16 Reconcile AM subledger with GL
17 Check Bank Data
18 Review AR Open Items
19 Review AP Open Items
20 Execute Pending Invoices
21 Clear Open Item for GRIR, freight
22 Reconciliation of Financial Documents and transactional figures
23 Open new CO Posting Period
24 Compare current (cost estimates) with last current price (Moving Avg)
25 Update current cost price to material master price field.
26 Process Freight charges, Match SD freight to actual
27 Review Internal Order Postings
28 Settle All Orders
29 Verify All Post Goods Issue have been Invoiced (Billing Due List)
30 Review SD Billng Doc from prior mth that have not yet been released to accounting
31 Reconciliation of MM movements in Transit Intra-SAP to NonSAP
32 Reconcile PI Inventory with SAP
33 Perform Manual Adjustment if needed
34 Verify balance of the GR/IR account
35 Post Accruals and Deferrals
36 Clearing of Cancelled Documents
37 Check Profitability Segment Adjustment
38 Aging Report-Reconcile GL balances with subledger balances AP
39 Check the check run numbers
40 Bank reconciliation Data
41 Enter Tax Journal Entry
42 Reconcile GL balances with subledger balances AR/MM/AP
43 Display Balance Sheet Adjustments
44 Post Balance Sheet Adjustments
45 Post Foreign Currency Valuation (foreign exchange)
46 Check generic cost centers for posting with wrong accounts
47 Correct wrong postings on generic cost centers
48 Check Validation dates for Cost Centers, Cost Elements, CO area
49 Check COGI--for both month end and year end
50 Doubtful receiviables
51 Verify In-transist Inventory
52 Reconcile PA to G/L
53 Post Cost Centre Assessments and Distributions
54 Run CO-FI Reconciliation to balance
55 Run BW reports P&L and Balance Sheet
56 Maintain CO yr variant
57 Fiscal Yr Balance carryforward AP/AR/AM
58 Fiscal Yr Balance carryforward CO
59 Fiscal Yr balance carryforward FI
60 Fiscal Yr balance carryforward PCA
61 Set Document number ranges - FI - new year
62 Set Document number ranges AP/AR - new year
63 Generate Financial statement Reports
64 Change Fiscal Year For Assets
65 Year end Closing-- Asset Accounting--final for year end
66 Close CO Posting Period
67 Close Prior A/R Posting Period
68 Close Prior A/P Posting Period
69 Close Prior MM Posting Period
70 Reverse accruals and deferrals for the new month
71 Reconciliation of Financial Documents from old fiscal year and new fiscal year
72 Load Balances, Budget Data for Cost centers, sales
73 Update Retained Earning Account , balance carry fwd
please reward points if useful.

ESYU: Returned, Finally Closed, Canceled 된 PR의 예산이 풀린것을 확인하는 방법

Purpose
Requisiton이 canceled, finally closed 되거나 혹은 buyer에 의해 returned 된 경우
PR에 적용된 예산이 풀린것을 어떻게 확인해야 되는가?
Solution
Canceled, Finally closed 혹은 buyer에 의해 returned 된 상태의 Requisition에 적용된
예산이 reversed 된 내용을 확인하는 방법에는 여러가지가 있다.
<Via the Purchasing Application>
1. Application에서 Requisition> Requisition Summary 화면으로 이동
2. Searhc criteria에 Requisition Number를 입력하고, distribution으로 이동하기 위해
Distribution button을 click
3. Distribution 화면이 조회되면, Folder/Show Field로 이동하여 "Reserved" 와
"Encumbered Amount' fileds를 조회
Note: 만일 위의 view를 folder로 저장한다면, "Include Query" checkbox는 선택하지 않아야 하고
Autoquery region의 "Never"는 선택해야 한다.
<Via SQL query>
이 정보는 주어진 Requisition의 requisition's encumbered status를 보기 위해 아래 tables의
조회를 통해 얻을 수 있다.
1. PO_REQ_DISTRIBUTIONS_ALL- 이는 위에 설명한 PR Summary distribution과 동일한 정보를
보여준다.
select encumbered_flag, encumbered_amount
from po_req_distributions_all
where requisition_line_id in (select requisition_line_id
from po_requisition_lines_all where requisition_header_id =
(select requisition_header_id from po_requisition_headers_all
where segment1 = '&reqnumber'))
2. GL_BC_PACKETS- 이는 Return, Final Close 혹은 Cancel action에 의해 생성된 records를
보여준다. 이는 GL에서 'Create Journal Entries Process'가 아직까지 실행되지 않았을 경우
에만 유효하다.
select *
from gl_bc_packets
where reference1 = 'REQ'
and reference4 = '&requisition_number'
양수 Entered_Dr이 조회되면 이는 각 distribution의 encumbrance amount를 의미한다.
음수 Entered_Dr이 조회되면 Cancellation에 의해 relief 된 encumbrance를 의미한다.
양수 Entered_Cr이 조회되면 이는 Return/Reject action이나 Final close action에 의해 relief 된
encumbrance를 의미한다.
Note: 만일 'Create Journal Entries Process'가 Requisition이 encumbered 된 시점과 canceled 혹은
Rerurned 된 시점 사이에 실행되었다면, 오직 가장 최근 actions에 대한 내용만이 이 table에서
보여줄 것이다.
최신의 완결된 그림은 'Create Journal Entries Process' 실행 후 GL_JE_LINES table 조회를
통해 얻을 수 있다.
3. GL_JE_LINES- 이는 Return, Final Close 혹은 Cancel action에 의해 생성된 records를 보여준다.
이는 GL에서 'Create Journal Entries process'가 실행된 이후에만 가용하다.
select *
from gl_je_lines
where reference_1 = 'REQ'
and reference_4 = '&requisition_number'
Note: GL queries에서 PO transacitons에 대한 reference values는 아래와 같다.
GL_BC_PACKETS/GL_JE_LINES
reference1/reference_1= Source (PO or REQ)
reference2/reference_2= requisition or purchase order header id
reference3/reference_3= requisition, purchase order or release distribution id
reference4/reference_4= requistion or purchase order number.
Reference
Note 337865.1

Stepper motor closed loop control using 7344

I have some question about the closed loop control of stepper motor using 7344. From the NI website I got that closed loop steppers work differently from closed loop servos. Instead of adjusting the output on each PID iteration like a servo system, closed loop steppers will do a pull-in move at the end of a move to adjust for any difference between the target position and the encoder feedback. By default, it will attempt the pull-in move three times.
Now for example I got five points: (0,0) (10,20) (30 40) ( 31 60) (50 65). The request time interval I set as 10ms. This mean that in the first 10ms, the machine should move from (0 0) to (10 20). But for some reasons the machine can not move to (10, 20), it moves to (8,16) and the first 10ms passed. In the second 10ms, how it move? Move from (8 16) to (30 40), If like this, the following error will accumulated. In practise, it is not accumulated. Is there anyone can explain something about the closed loop control of stepp motor? Thanks a lot!

Requested Interval is additional data for the Position buffer type. The Position buffer type requires a Requested Interval parameter, and indicates the time between contouring data points in milliseconds. For all other buffer types, the Requested Interval parameter is ignored.
The controller will use the closest value it can that is greater than or equal to the interval value you requested. Your time interval must be an even multiple of the PID rate.
For example, given a PID rate of 250 ms, a time interval of 11.2 ms between points is physically impossible, so a call to configure buffer with an interval of 11.2 causes the buffer to actually be configured for 11.25 ms, since 11.25 is the nearest possible interval greater than 11.2. The following table shows valid intervals for each PID rate.
My question is like this. For example I got five points: (0,0) (10,20) (30 40) ( 31 60) (50 65). The request time interval I set as 10ms. This mean that in the first 10ms, the machine should move from (0 0) to (10 20). If it is impossible for the machine to move from (0 0) to (10 20), there are two ways to solve this problem. First is the time interval is 10ms and assume it move to (8 16) within 10ms and take (8 16) as the start point and (30 40) as the end point of the second move. Second is extend the time interval, assume it takes 14ms to move from (0 0) to (10 20). After 14ms, the (10 20) is the new start point for the second move. I think it works as the second ways.If not, the following error will accumulated. Is there anyone can explain something about the closed loop control of stepp motor in detail? Thanks a lot!

Closed loop control of step motors possible with 7344?

Hi All
I have been looking around here for a while for an answer to this question.
For me, a closed loop control system is correcting for following errors all the time, also when the move is complete.
If the load on a system changes, there will often be a need for compensation in order to keep the position right. Then you need a closed loop control system.
I have made a system using DC motors with a 7342 controller. We are in the process og getting a new similar system, where the manufacturer chosed stepmotors in the believe that it can be used in closed loop.
Is it really true that the NI version of closed loop is only performing a what you call a "pull-in" at the end of the move in order to correct for lost steps or flexibility of the connection between motor and object/encoder?
I would call this "backlash compensation" or something like that.
Why dont you make a real closed loop option. The control voltage from your servo motor control, could be fed into a voltage-frequency converter with a matchin sign signal.
This shouldn't be too complicated to accomplish.
/b

You are right. NI motion control boards don't apply a control algorithm
during moves when configured in closed loop stepper mode. In this mode
the board monitors the following error during the move and generates an
error when the following error limit is exceeded and they start the
pull-in moves at the end of the move if necessary.
If you really want to do PID control with stepper motors you still
could connect an external V/f converter to the DAC outputs of the board
and control the axes like DC motor axes. Some vendors implement this
feature on their board but NI has decided not to do that as we don't
think that this approach provides a good solution. Here are some reasons:
The most important issue is the fact that you could easily exceed
the maximum rate of change of the motor frequency in the case that the
following error increases during the move. For a DC motor this would mean that the
voltage of the controller increases to compensate for this error and
the motor will follow - probably with some delay, but it will follow. For
the stepper this could mean that the acceleration becomes so high
that the motor stops immediately as it can't follow with a delay like a DC motor. What
should the controller do then? Restart the move automatically? Generate
an error? There is a big chance that you end up with a system moving in a stop and go mode.
The second issue is related to the control algorithm itself. The transfer function of a stepper motor is not really linear so it will be quite hard to find good tuning parameters. A DC motor can be tuned by analyzing the step response and the Bode plot. For the reasons that I have described in 1.) this won't work for a stepper so how should you tune it?
I have talked to some motion control engineers who have tried to control steppers with a PID algorithm and they all agree that this is a real pain and it's not recommended.
So if your system requirements involve online following error compensation I strongly recommend using a DC motor.
Best regards,
Jochen Klier
National Instruments Germany

How do you cancel an invoice on a finally closed PO? - URGENT

We attempted to void and cancel a check and Oracle allowed the void, but did not allow the invoice to be cancelled. Further investigation revealed that the associated PO had been finally closed. We were unable to enter a credit in the distribution because it wouldn't allow the invoice amount to be changes so that it would go on hold. Since the PO can't be reopened after being finally closed, how should this invoice be handled?

The user finally got back to me on the proposed solution, but it doesn't completely solve her problem.
The transaction is in limbo because we've voided the check now but it won't let us create the accounting to complete the void.
Because of this – it's in limbo and continues to be "swept" each month into the next accounting period. We need to find a way to complete this void transaction so it won't keep showing up as a reconciliation item.

PO when Finally Closed not releasing funds

In 11.5.9; if we final close a PO using standard "po_actions.close_po" procedure, the PO used to get Finally Closed and corresponding Funds get released.
However, the same does not work in 11.5.10.
I would be glad if anyone can help me in this regard. Please note that we are using encumbrance feature; hence it is a very critical issue.
Thanks,
M. Geethanath
[email protected]

In 11.5.10 PO Final Close process works well only when we invoke PO_ACTIONS.CLOSE_PO procedure by passing PO Header-ID, Line-ID and Line Location-ID.
It is because of below code:
PO_DOCUMENT_FUNDS_PVT.do_final_close(
x_return_status => l_return_status
, p_doc_type => p_doctyp
, p_doc_subtype => p_docsubtyp
, p_doc_level => PO_DOCUMENT_FUNDS_PVT.g_doc_level_SHIPMENT
, p_doc_level_id => p_shipid
, p_use_enc_gt_flag => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_use_gl_date => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_override_date => p_action_date
, p_invoice_id => p_origin_doc_id
, x_po_return_code => l_return_code
, x_online_report_id => l_online_report_id
If the above call was to decide on Document Level based on the values held by below variables, it would have been more appropriate.
p_docid (PO Header ID)
p_lineid (PO Line-ID)
p_shipid (PO Line Location-ID)
Example:
IF p_shipid IS NOT NULL THEN
PO_DOCUMENT_FUNDS_PVT.do_final_close(
x_return_status => l_return_status
, p_doc_type => p_doctyp
, p_doc_subtype => p_docsubtyp
, p_doc_level => PO_DOCUMENT_FUNDS_PVT.g_doc_level_SHIPMENT
, p_doc_level_id => p_shipid
, p_use_enc_gt_flag => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_use_gl_date => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_override_date => p_action_date
, p_invoice_id => p_origin_doc_id
, x_po_return_code => l_return_code
, x_online_report_id => l_online_report_id
ELSIF p_lineid IS NOT NULL THEN
PO_DOCUMENT_FUNDS_PVT.do_final_close(
x_return_status => l_return_status
, p_doc_type => p_doctyp
, p_doc_subtype => p_docsubtyp
, p_doc_level => PO_DOCUMENT_FUNDS_PVT.g_doc_level_LINE
, p_doc_level_id => p_lineid
, p_use_enc_gt_flag => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_use_gl_date => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_override_date => p_action_date
, p_invoice_id => p_origin_doc_id
, x_po_return_code => l_return_code
, x_online_report_id => l_online_report_id
ELSIF p_docid IS NOT NULL THEN
PO_DOCUMENT_FUNDS_PVT.do_final_close(
x_return_status => l_return_status
, p_doc_type => p_doctyp
, p_doc_subtype => p_docsubtyp
, p_doc_level => PO_DOCUMENT_FUNDS_PVT.g_doc_level_HEADER
, p_doc_level_id => p_docid
, p_use_enc_gt_flag => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_use_gl_date => PO_DOCUMENT_FUNDS_PVT.g_parameter_NO
, p_override_date => p_action_date
, p_invoice_id => p_origin_doc_id
, x_po_return_code => l_return_code
, x_online_report_id => l_online_report_id
END IF;
Anyways, it is not categorized as a Public API; so, no comments…
Please find below sample procedure that can be re-used.
PROCEDURE fclose_po (
p_po_header_id NUMBER,
p_po_line_id NUMBER DEFAULT NULL,
p_reason VARCHAR2,
p_close_date DATE
IS
CURSOR c_shipments
IS
SELECT po_header_id, po_line_id, line_location_id
FROM po_line_locations_all
WHERE po_header_id = p_po_header_id
AND po_line_id = NVL (p_po_line_id, po_line_id);
BEGIN
FOR c1 IN c_shipments
LOOP
IF (NOT (po_actions.close_po (p_docid => p_po_header_id,
p_doctyp => 'PO',
p_docsubtyp => 'STANDARD',
p_lineid => c1.po_line_id,
p_shipid => c1.line_location_id,
p_action => 'FINALLY CLOSE',
p_reason => p_reason,
p_calling_mode => 'PO',
p_conc_flag => 'N',
p_return_code => v_return_code,
p_auto_close => 'N',
p_action_date => p_close_date,
p_origin_doc_id => NULL
THEN
l_status := 'ERROR';
ELSE
l_status := 'SUCCESS';
END IF;
END LOOP;
END fclose_po;

PO when Finally Closed does not release funds

In 11.5.9; if we final close a PO using standard "po_actions.close_po" procedure, the PO used to get Finally Closed and corresponding Funds get released.
However, the same does not work in 11.5.10.
I would be glad if anyone can help me in this regard. Please note that we are using encumbrance feature; hence it is a very critical issue.
Thanks,
M. Geethanath
[email protected]

In 11.5.9; if we final close a PO using standard "po_actions.close_po" procedure, the PO used to get Finally Closed and corresponding Funds get released.
However, the same does not work in 11.5.10.
I would be glad if anyone can help me in this regard. Please note that we are using encumbrance feature; hence it is a very critical issue.
Thanks,
M. Geethanath
[email protected]

I have a trial version of final cut pro x. i purchased a serial number. where do i enter it.

i have a trial version of final cut pro x. i purchased a serial number for it. where do i enter it?

Not sure what you purchased but it wasn't a serial number. FCPX has no serial number. You simple download it from the App Store using your Apple ID.

Cancell/Open finally closed PO

Hi
how do we cancell/Open finally closed PO,...if it can't be done then how do we reverse the funds already reserved?
this is rather urgent guy
thank you in advance

Hello,
For finally closed PO, I had the problem and I ask to the support on Metalink.
I obtain the normal answer : "it is not possible" (which is of course the most reasonable) ... and the "unsupported" answer :
--po_header_id = 10648
-- Back Up data
CREATE TABLE TAR_6634712_993_PLLA
AS SELECT * FROM po_line_locations_all
where po_header_id= 10648;
CREATE TABLE TAR_6634712_993_PLA
AS SELECT * FROM po_lines_all
where po_header_id= 10648;
CREATE TABLE TAR_6634712_993_PHA
AS SELECT * FROM po_headers_all
where po_header_id = 10648;
-- Update
update po_line_locations_all
set closed_code='', closed_date=''
where po_header_id= 135840;
update po_lines_all
set closed_code='', closed_date=''
where po_header_id= 135840;
update po_headers_all
set closed_code='', closed_date=''
where po_header_id = 135840;Of course it should be carefully tested on your test environment !
Regards,
Xavier

Finally Closed PO need to Open

Hi,
User wants open finally closed PO ( encumbrance enabled) . More then 100 po like this finally closed. I know oracle metalink / SR won't support open PO from back end. I need either back end or Application level PO open steps or SQL. Please help me.
Thanks and regs
Ram

Oracle corporation does not provides any solution for this issue. I have personally develop SQL script. I have check it in Test Instance, its work.. Check it in your environment, whether its OK or not.
select * from PO_HEADERS_ALL he
where he.po_header_id = 126118
create table po9826_header
as select * from PO_HEADERS_ALL he
where he.po_header_id = 126118
update PO_HEADERS_ALL he
set he.closed_code = 'OPEN', he.closed_date = null
where he.po_header_id = 126118
select * from po_lines_all li
where li.po_header_id = 126118
create table po9826_line
as select * from po_lines_all li
where li.po_header_id = 126118
update po_lines_all li
set li.closed_date = null, li.closed_flag = null, li.closed_code = 'OPEN', li.closed_by = null
where li.po_header_id = 126118
select * from po_line_locations_all loc
where loc.po_header_id = 126118
create table po9826_location
as select * from po_line_locations_all loc
where loc.po_header_id = 126118
update po_line_locations_all loc
set loc.closed_flag = null, loc.closed_code = 'OPEN', loc.closed_date = null, loc.closed_by = null,
loc.closed_for_receiving_date = null, loc.closed_for_invoice_date = null
where loc.po_header_id = 126118
select * from po_action_history re
where re.object_id = 126118
and re.employee_id = 3711
create table po9826_actionhistory
as select * from po_action_history re
where re.object_id = 126118
and re.employee_id = 3711
delete from po_action_history re
where re.object_id = 126118
and re.employee_id = 3711
Regards
Omer
---------------------------------------------------------------

Closed loop control of DC motor drive using PCI 6251

Hi
i am using NI PCI 6251 for closed loop control of dc drive.(shunt motor,220v, 0.5HP, 2.5A rated, 1500RPM)
the dc motor is fed from a bidirectional dc-dc converter. this converter works in boost mode(forword motoring) and buck mode(braking mode/battery charging)
the converter is built using mitsubishi IGBT module. at low voltage side of the converter a battery bank of 48V is connected and high voltage side the motor is connected.
An IR sensor is developed to measure the speed of the motor and a hall current sensor is used to sense the converter current.
in the control part i have an inner current control loop(PWM controller) and a outer speed control loop.both controllers are PI controller. To measure the speed i have used counter of the DAQ assistant, then frequency. then this frequency is converted to RPM using labview.after giving the speed and current signals to the controllers , then i started tunning the PI gain, but at the starting the duty cycles was 100%, so the IGBT got damaged immediately. now how to tune the controllers during the closed loop operation. the switching frequency of the converter is 20KHz.
can any body suggest me how to run the dc drive in closed loop ?
thanking you.

Hi Premenanda
The freq data receiverd from the daq assistant has the units of Hz, or in terms of motor speed, rps (rotations per second). I can see that you are trying to convert that to rpm (rotation per minute). which can be done by dividing the rps speed by 60. Instead, you are multiplying it by 60 and also comparing with 2000. the resultant multiplied value is displayed in your program only if it is smaller than 2000.which is causing the problem here.( as seen in file 'original code.png)
I have attached a file named 'modified code.png' that shows how the conversion from rps to rpm is done. Please do the required changes in your code and let me know if it works.
Attachments:
modified code.png ‏18 KB
Original code.png ‏15 KB

Finally Closed setup control in Purchasing

Similar Messages

Maybe you are looking for