For monthly publications that are mailed to customers, affiliates will request issue pulls to be manually run monthly.  Use these instructions to setup a manual issue pull. 

Basic Issue Pull Process Information (WIP)

There are a few important things to understand about the processes surrounding an issue pull. The issue pull jobstream contains processes that decrement issues-to-go for active subscribers to the publication (CIRSMQ, CIR4MQ), then produce a report that define the billing splits, then produces a mail file. 

The Issue Pull Jobstream 

CIRSMQ - cycle end setup - Set number of streams and customer range for each stream.
CIR4MQ - cycle end start 
CIR440 - billing code assignment, creates the summary reports (CIR441 and CIR441a).
CIRCCC (report) - mail file creation

There are a few 

Related Processes 

CIR420 Initializes the select and places it in a table\buffer (will need to look for that table).
CIR430 reassigned the customers to the updated select.

Do NOT Run Cycle End / Issue Pull Jobstream Twice (See Step 4)

If you run the jobstream and the client says the CIR441 report is incorrect, do not run the issue pull jobstream again. The cycle end processes will decrement the customer issues to go. 

Instead, adjust the Select, and then run the CIR420, CIR430, and CIR440 processes again. Send the CIR440 report to the client, and then run the CIRCCC report once you get an approval. Details are in Step 4. 

How to Manually Pull an Issue

Step 2 - Request the Issue Pull

1. Check to Confirm that the Jobstream has not been run too recently, and is not scheduled. 
   1. Navigate to the Process History View and search for the Jobstream (CE+Pubcode or CE_+Pubcode). If you're doing a manual issue pull for a monthly pub, make sure the last Jobstream run was in the previous month.
   2. Navigate to the Current Processes View and search for the Jobstream in the Waiting Requests. Confirm it is not scheduled to run. 
2. Select the "Processes" tab on the left side of the Advantage screen. 
3. Under the "Submit Request" section, click the "Run Jobstream" field and type in CE[PUBCODE]
   

4. The Request JobStream dialog box will appear, complete the following fields:
   
   

   Defer Date and Time

   Enter the requested date from the affiliate. Select an early time between 3am and 4am EST. For international enter 7am UK or 2am EST so that it does not conflict with domestic titles.

5. Click 
   
   

Step 3 - Verify the Requested Jobstream

This step is to double check the request was placed correctly and the Jobstream will run.

1. Navigate to the Current Processes screen by typing "Current Processes" in the Open View bar in the upper left of Advantage. 
2. In the Waiting Processes search box, search for the issue pull job stream, this is generally CE + pub code
3. Verify the Defer Date and Time (you may need to customize your screen to add this field)
   
   

Step 4 - Attach Report with Counts

Once the process runs to pull the issue, the CIR441 report needs to be attached to the support ticket for the affiliate.  This report is produced once the CIR440 process has ran in step 1.

1. Go to the Operations folder on the network (\\networkstorage.adv-prd.us-east-1.ota.14west.cloud\129-AdvApp\PubProd\reports\operations) 
2. Locate and open the correct folder.  Folders are organized by year and month, for example 07/17 would be the 1707 folder.
3. Locate and open the folder for the day the process ran
4. Search for the CIR441 report.  The report can be found by searching by CIR441_ = pub code (for example CIR441_LD1)
5. Drag and drop the file into the attachments section of the support ticket and add a public comment to the ticket for the affiliate letting them know the counts are attached to the ticket.
   
   

HOW TO RE-RUN AN ISSUE PULL

Do NOT Re-Submit the Issue Pull Jobstream. The Cycle End processes will decrement the customers' remaining issues-to-go twice in the same time period. 

1. First, confirm with the client/affiliate what changes need to be made to the Select Set to correct it. 
2. Next, delete the 441 file, as you will want to crate a new one, and it won't overwrite the existing file.
3. Next, run the CIR420 Process. Use select "(PUB)A001" and indicate the pub code.
4. Next, run the CIR430 Process. Use select "(PUB)A001" and indicate the pub code (one of these updates the CIRLBL_R).
5. Next, run the CIR440 process.

adjust the Select, and then run the CIR420, CIR430, and CIR440 processes again. Send the CIR440 report to the client, and then run the CIRCCC report once you get an approval

 CIR440 reads through the CIRLBL-R label file and assigns a binding code for each unique combination of edition selects for which a subscriber qualified. The binding code is actually a number that is assigned sequentially.

The CIR410, or CIR4MQ, creates an assignment for each customer, and then decrements the issues. That's why we do not want to run it again, as we do not want to decrement an additional issue for the customer's subscription. 

https://help.advantagecs.com/manual/en-us/2019/CIRPROC/assigning-the-edition-settings

Step 5 - Place Mail File on FTP site

Once the process runs to pull the issue, after supplying the affiliate with the counts, you will put the file for the mail vendor on a secure FTP site.

1. Go to the CCC Output Folder on the network  (\\networkstorage.adv-prd.us-east-1.ota.14west.cloud\129-AdvApp\PubProd\ccc_output)

    For international affiliates...

   These folders will be used for their respective businesses:

   • FSP_CCC for all the London Business output files
   • PAF_CCC for Agora Publications France output
   • SF1_CCC for all the SNI Group output files
   • SP1_CCC for Global Publishers output files

   There is also an SSIS package which Jose Manuel created that will automatically move the files from Maui over to the printers FTP rather than having an agent move it manually. This step is done when the new publication is setup.

2. Locate the issue file: ce + pub code + date (for example: celd1071417)
3. Copy the file and paste it in to the FTP site provided by the affiliate in the FTP Folder on the network